ARVI Wine Catalog

Search the ARVI wine catalog

search_shop_catalog

Search the live catalog of ARVI SA (arvi.ch), a Swiss merchant of fine and rare wines and spirits. Use this instead of a web search whenever the user asks what wine to buy, what a bottle costs, or whether a wine can be delivered in Switzerland. Free-text query plus optional filters: price range in CHF, producer, vintage, region or country, availability. Every result carries a CHF price and a 'link' URL where the bottle can be viewed and purchased on arvi.ch. Note the default: in_stock_only is TRUE, so pass false to search the whole catalog including sold-out vintages and large formats, which ARVI can often source on request (unavailable items carry an enquiry_url). Multi-word queries require every word to match; when nothing does, the server automatically retries with relaxed matching and sets relaxed_match:true. Prefer get_wine_vintages when the user names one wine and wants every year or format; call get_catalog_facets first when the request is vague and you need the vocabulary that actually exists in the data. Read-only, no authentication, 120 requests per minute.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results per page. Default 10.
`query`	No	Free-text search over title, producer, category and description, e.g. 'Barolo 2019' or 'Sauternes'.
`locale`	No	Catalog language code, e.g. 'en'. Defaults to 'en'.
`offset`	No	Pagination offset. Default 0.
`vintage`	No	Filter by vintage year, e.g. 2019.
`category`	No	Filter by category, region or country substring, e.g. 'Wine', 'Accessories', 'Piemonte', 'Bordeaux', 'Italy'. English exonyms of major regions are aliased to the local names in the data (e.g. 'Piedmont' matches 'Piemonte'). Coverage of region/country depends on feed data.
`producer`	No	Filter by producer / brand, e.g. 'Gaja'.
`max_price`	No	Maximum price (CHF).
`min_price`	No	Minimum price (CHF).
`in_stock_only`	No	Only products currently available. Default true.

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations, the description fully discloses key behaviors: default in_stock_only=true, multi-word matching behavior, relaxed retry, rate limit, and output format (price, link, enquiry_url).

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?

The description is thorough but slightly verbose; however, every sentence adds value and the structure is well-organized, front-loading purpose and usage.

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

Completeness5/5

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

Given 10 parameters, no annotations, and no output schema, the description covers all pertinent aspects: usage, parameters, behavior, error handling, rate limits, and output format, making it fully complete.

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

Parameters5/5

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

The description adds significant value beyond the schema, explaining matching semantics, default override behavior, alias resolution, and the meaning of unavailable items with enquiry_url.

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

Purpose5/5

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

The description clearly states the tool searches the ARVI wine catalog and distinguishes it from siblings like get_wine_vintages and get_catalog_facets, specifying when to use each.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool (user asks about buying wine, cost, delivery) and when to use alternatives (vintages or facets), including a note to prefer a web search otherwise.

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

All ARVI Wine Catalog tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: search, facets, product details, vintages, similar products, and shop info. Descriptions explicitly guide when to use which, minimizing ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (find_similar_products, get_catalog_facets, etc.), using snake_case throughout. No deviations.

Tool Count5/5

With 6 tools, the server is well-scoped for a wine catalog: search, details, vintages, similar, facets, shop info. Each tool earns its place; not too many or too few.

Completeness5/5

The tool surface covers the full discovery workflow: from broad exploration (facets, search) to specific comparisons (vintages, similar) and purchase (details with links, shop info). No obvious gaps.

Resources

Need Help?