Skip to main content
Glama

ARVI Wine Catalog

by ch.arvi

Get one product

get_product_details

Full record for one product id returned by search: description, producer, vintage, bottle format, price in CHF, availability and the exact purchase link. Call it before recommending a specific bottle, so the answer carries the real tasting/estate description and a link the user can buy from, instead of a summary. For every vintage of the same wine use get_wine_vintages; for alternatives use find_similar_products.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct id from search results.
localeNoCatalog language code. Optional.

TDQS

A4.5/5.0
Behavior4/5

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

No annotations, but description fully explains what is returned (fields including purchase link and real tasting description). Idempotent read behavior is implied. Could mention no side effects, but sufficient.

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

Conciseness5/5

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

Three sentences: output fields, use case, alternatives. No wasted words, front-loaded with purpose.

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?

Complete for a simple read tool with 2 params and no output schema. Lists return fields, use case, and sibling differentiation.

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 coverage 100%, so baseline is 3. Description restates that id comes from search results, which is already in schema. No additional parameter meaning beyond schema.

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?

Clear verb+resource: returns full record for a product id. Lists fields and distinguishes from siblings like get_wine_vintages and find_similar_products.

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?

Explicit when to call ('before recommending a specific bottle') and when not to (use get_wine_vintages for vintages, find_similar_products for alternatives).

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 toolsInspect
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