Red Good Wine

Search bottles

search_bottles

Read-onlyIdempotent

Search the Red Good Wine index of wine, beer, spirits and zero-proof bottles from independent US shops by name, producer, grape, region or style, optionally by category, style and a maximum price.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_bottles"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results (default 10).
`query`	No	Words to match: a name, producer, grape, region or style.
`style`	No	Wine style.
`category`	No	wine, fine-wine, beer, spirits, non_alc (zero-proof), food (pantry) or gear.
`max_price_usd`	No	Only bottles whose lowest shop price is at most this.

Output Schema

Name	Required	Description	Default
`count`	Yes
`bottles`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

changedInput schema / properties / max_price_usd / description

Previous value: -"Only bottles whose best shop price is at most this."New value: +"Only bottles whose lowest shop price is at most this."

First observedNov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety behaviour is covered. The description adds that the corpus is independent US shops, which is real context, but says nothing about ordering of results, empty-result behaviour, or pagination beyond the schema's limit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence that puts the resource and the search facets before the optional filters. It is slightly over-packed with enumerations that repeat the schema, but nothing is genuinely wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full parameter coverage, the description only needs to convey scope and matching behaviour. It does that for the corpus and facets, though it could state what happens when no filters are supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented in structured data. The description restates the searchable fields (name, producer, grape, region, style) and the optional filters without adding format or matching semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (search) plus resource (the Red Good Wine index of wine, beer, spirits and zero-proof bottles from independent US shops) and the searchable facets. An agent immediately knows the operation, but no sibling is named, so the boundary with recommend_bottles or best_price must be inferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase 'optionally by category, style and a maximum price', which tells the agent filters are additive rather than required. There is no explicit when-to-use or when-not-to-use versus the sibling tools, so selection guidance is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Red Good Wine tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?