Loading ToolBench
carsensor.net の相場(souba)ページから車種×年式の市場価格レンジを返す、単一ツールのMCPサーバー。ローカルstdio起動(mcpServer.js)とApify Actor/Standbyモード経由のHTTPホスティング(src/main.js)の両方に対応。
Single tool 'resolvePriceRange' has a well-structured description (Japanese, ~180 chars) and explicit input schema with Zod validation. However, the schema uses Zod's `.describe()` method rather than JSON Schema format visible in the MCP registration, making it harder to verify parameter descriptions are properly exposed to clients. Output schema is not documented, the tool returns a JSON object with 'ok', 'reason', and price fields, but this structure is not formally declared. Error handling is present (ok:false with reason field) but lacks actionable recovery guidance. No tool annotations (readOnlyHint, etc.) despite being READ_ONLY.
車種名と年式から、carsensor.net自身が公開する相場(souba)ページの「価格×年式」集計データを基に、市場価格レンジ(最小・最大・中央値)を返す。carsensorの検索結果から車種を特定できない場合、または該当年式の相場データが無い場合はok:falseで理由を返す。走行距離は未対応(v2で追加予定)。
Output schema not documented. Tool returns {ok, reason, min, max, median} but LLM has no formal schema to plan downstream calls or extract fields reliably.
Error responses lack actionable recovery guidance. When ok:false, reason field is present but tool description does not explain what the LLM should do next (e.g., 'Try a different car model spelling' or 'This year has no market data').
Tool annotations missing. Tool is READ_ONLY but does not declare readOnlyHint:true in schema, preventing clients from optimizing caching or parallelization.
Parameter descriptions in Zod schema may not be exposed to MCP clients. The inputSchema object uses Zod's .describe() but the actual JSON Schema sent to clients is not visible in source, verify that descriptions are serialized correctly.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | <=2025-11-25 | v2 |
No pagination or result limits documented. Tool returns a single price range, but if future versions support multiple matches or batch queries, lack of pagination guidance will cause context window issues.