Tasters

Remove a wine from my cellar

remove_from_cellar

DestructiveIdempotent

Delete a wine from the user's cellar entirely, including its history. Only call this when the user explicitly asks to remove or delete it, and confirm with them first. To record that a bottle was drunk, use drink_from_cellar instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ref": "<ref>"
    },
    "name": "remove_from_cellar"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes	Wine slug, as returned by `search`, `recommend_wines` or `list_cellar`.
`locale`	No	Content language: fr, de, en or it. Refs returned by `search` are locale-specific, so pass the same locale to the get_* tools.	fr

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description adds context beyond them: it discloses that history is destroyed along with the wine and that the user must be confirmed first. That is precisely the kind of consequence and authorization context an agent needs for a destructive operation.

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 short sentences, front-loaded with the destructive scope, then the usage condition, then the sibling alternative. Every sentence carries distinct decision-relevant information.

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 destructive two-parameter tool: the description covers what is deleted, the confirmation prerequisite, and the alternative for a related intent, while annotations and the schema cover safety and parameters. No return value is needed for a delete operation.

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% and both parameters are documented in the schema, including the enum and the note that refs are locale-specific. The description adds no parameter-level meaning beyond the schema, 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?

Names a specific verb ('Delete') and resource ('a wine from the user's cellar') and adds the crucial scope detail that the wine's history is removed entirely. It explicitly contrasts itself with the sibling tool drink_from_cellar, so an agent can distinguish the two without opening either 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?

Explicitly states the when condition ('Only call this when the user explicitly asks to remove or delete it'), adds a confirmation requirement, and names the correct alternative for a different intent ('To record that a bottle was drunk, use drink_from_cellar instead').

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

All Tasters 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?