NEVINI Wines

Catalog overview

get_catalog_overview

Read-onlyIdempotent

Returns an overview of the NEVINI range: wine counts per type, country and category page, the most common grapes, the top selection and the verified price range. Use it to see what the range covers; use search_wines to find wines and get_wine for one wine.

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": "get_catalog_overview"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Response language: "nl" (Dutch, default) or "en" (English).

Output Schema

Name	Required	Description	Default
`notes`	Yes
`types`	Yes
`commerce`	Yes
`language`	Yes
`countries`	Yes
`categories`	Yes
`top_grapes`	Yes
`total_wines`	Yes
`top_selection`	Yes
`price_range_eur`	Yes
`purchasable_wines`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile needs no restating. The description adds that this is an aggregate/statistics view rather than a wine list, which is useful framing, but says nothing about cost, caching, or how the aggregate is scoped (whole catalog vs. filtered).

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?

Two sentences, both front-loaded: the return content first, the routing guidance second. Every clause earns its place with no filler.

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?

The tool takes no required parameters, has an output schema, and the description supplies sibling routing. Nothing an agent needs in order to call this correctly is missing.

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 is 100% and the single 'language' parameter already documents its enum and Dutch default. The description adds no further parameter meaning, so the baseline of 3 applies.

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?

Specific verb and resource ('Returns an overview of the NEVINI range') plus the concrete contents of that overview: counts per type, country and category, common grapes, top selection, price range. It also explicitly distinguishes itself from search_wines and get_wine, so an agent can route without opening a schema.

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?

States exactly when to use it ('to see what the range covers') and names both alternatives with their own conditions ('search_wines to find wines, get_wine for one wine'). No inference required to choose among siblings.

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

All NEVINI Wines 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?