wine_recommendationFetch specific wine product recommendations for a wine type name (e.g. "merlot", "chardonnay") with optional minRating, price target, and number of results. Returns product name, price, average rating, and description.
| Name | Required | Description | Default |
|---|---|---|---|
| wine | Yes | ||
| price | No | ||
| number | No | ||
| minRating | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "wine": "Cabernet Sauvignon"
+ },
+ {
+ "minRating": 4,
+ "number": 5,
+ "wine": "Pinot Grigio"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "description": "Wine recommendations",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds value by disclosing the return fields (product name, price, average rating, description) and the optional filter parameters, which are not fully implied by the annotations alone.
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?
The description is two sentences, front-loaded with the action and an example, with no redundant phrases. Every sentence contributes to understanding the tool's purpose and parameters.
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?
Given the tool's simplicity, the presence of an output schema, and the rich annotations, the description is complete. It covers the purpose, parameters, and return values, and does not need to explain output format detailed in the schema.
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?
With 0% schema description coverage, the description carries the burden of explaining parameters. It names all four parameters and gives each a semantic role: 'wine type name', 'minRating', 'price target', and 'number of results'. This adds meaning beyond the raw schema names, although it does not specify formats or constraints (e.g., price string format).
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?
The description clearly states the tool fetches specific wine product recommendations by wine type name, using a specific verb ('Fetch') and resource ('wine product recommendations'). It is well-distinguished from sibling tools like wine_pairing, which focuses on pairings rather than product recommendations.
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?
The description provides clear context for when to use the tool: when you have a wine type name and want product recommendations, with optional filtering by rating, price, and number. It does not explicitly mention alternatives or exclusions, but the use case is unambiguous and self-contained.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.