wine_pairingFetch wine pairing suggestions for a food dish or ingredient (e.g. "salmon", "pasta primavera") with optional maxPrice filter. Returns paired wine types and specific product recommendations with name, price, and description.
| Name | Required | Description | Default |
|---|---|---|---|
| food | Yes | ||
| maxPrice | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "food": "salmon"
+ },
+ {
+ "food": "steak",
+ "maxPrice": 50
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "description": "Wine pairing recommendations",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish this as read-only, idempotent, open-world, and non-destructive. The description adds behavioral context by specifying that it returns 'paired wine types and specific product recommendations with name, price, and description', which goes beyond the annotations but doesn't introduce new safety concerns. No contradictions.
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?
Two sentences: first sentence states purpose and parameters, second describes the return. Front-loaded, no fluff, examples embedded inline. Efficient and well-structured.
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?
For a 2-parameter, read-only tool with output schema present and strong annotations, the description covers the core functionality, parameters, and return type. It is complete enough for an agent to decide and invoke correctly. No significant gaps.
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 compensates by explaining that `food` is a dish or ingredient and `maxPrice` is an optional filter. It provides examples ('salmon', 'steak' with maxPrice 50) that clarify parameter usage, though it doesn't specify units or behavior for maxPrice.
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 uses the specific verb 'Fetch' and clearly identifies the resource: 'wine pairing suggestions for a food dish or ingredient', with examples. It clearly communicates the tool's function but does not explicitly differentiate from the sibling tool 'wine_recommendation', so it stops short of full differentiation.
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 implies its usage context—when you need wine pairing suggestions for a specific dish—but provides no explicit when-to-use or when-not-to-use guidance, and does not mention alternatives like 'wine_recommendation'.
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.