Loading ToolBench
A price tracking service that monitors competitor product prices and calculates price differences
This MCP server has a single tool with minimal definition quality. The tool lacks a proper MCP server implementation entirely, it's just a Python class with no MCP protocol integration. The input schema is provided but descriptions are extremely sparse. The tool does one thing (track price) but lacks the documentation, error handling, and composition expected of production-grade agent tools. No evidence of MCP server initialization, tool registration, or protocol compliance in the source code.
Tracks competitor product prices and returns price difference percentage
No MCP server implementation detected. Source contains only a Python client class (PriceTrackerClient) with no MCP protocol integration, transport layer, or tool registration mechanism. Cannot function as an MCP server.
Tool description is only 91 characters and lacks context for agent selection. Does not explain WHEN to use this tool vs. alternatives, what prerequisites exist, or what the output fields mean. Baseline: A+ tools average 194 chars; descriptions under 20 chars cannot exceed 40/100.
Input schema has no descriptions for parameters. 'product' and 'competitor_url' lack any guidance on format, constraints, or expected values. LLMs cannot infer whether to pass SKU codes, product names, full URLs, or relative paths.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 34 | 2026-07-28+ | v2 |
No output schema documented. The tool returns {'price_diff_pct': -12.5} but this structure is not formally declared. Agents cannot plan downstream operations or extract fields reliably. Baseline: 100% of A+ tools document return types.
No error handling or recovery guidance. If the URL is unreachable, the product is invalid, or the price data is unavailable, there is no error classification, retryable status, or next-step suggestion for the agent.
Tool name 'track_price' starts with verb but lacks clarity on scope. Does 'track' mean monitor over time, fetch current price, compare against historical baseline, or alert on changes? Ambiguous naming forces LLMs to guess.
No parameter type constraints. The 'competitor_url' parameter accepts free-form strings with no format validation, regex pattern, or URL scheme requirement documented. The 'product' parameter has no length, character, or format constraints.
No tool annotations present. The tool performs a read-only operation but does not declare readOnlyHint in the schema, preventing agents and clients from optimizing caching, replay, or auditing strategies.