Calculates min, median, max, and mean prices plus cheapest and priciest items from the first page of Migros search results for a keyword (up to 36 products).
Price statistics (min/median/max/mean, cheapest & priciest) for a keyword's first page of Migros search results (up to 36 products).
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It does disclose an important non-obvious trait — statistics cover only the first page, capped at 36 products — which prevents the agent from treating results as catalog-wide. However, it says nothing about read-only nature, whether a live search is triggered per call, or failure behavior when a query returns no matches.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One front-loaded sentence listing the metrics, the target, and the sampling limit with zero redundant wording. Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and the description enumerates the computed statistics. What remains thin is the parameter and error-path context, but for a one-parameter statistical helper this is close to complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'query' has no schema description (0% coverage), so the description must compensate. It does clarify that the value is a search keyword whose first page is analyzed, but does not specify language, matching semantics, or formatting for the query string.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource and operation: computes price statistics (min/median/max/mean, cheapest and priciest) over a keyword's first page of Migros search results. This implicitly distinguishes it from migros_search_products (which returns products) without naming that sibling explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: an agent can infer this is for summarizing price distribution rather than listing products. There is no explicit when-to-use/when-not-to-use guidance and no mention of the sibling tools that would be the alternative for getting the underlying products.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.