Skip to main content
Glama

GATA Cafeteras

Capsule compatibility

capsule_compatibility
Read-onlyIdempotent

Which capsules fit which machine: Nespresso Original vs Vertuo, Nescafé Dolce Gusto (classic) vs NEO, Tassimo T DISC, Philips SENSEO pads and K-fee. Returns how the system brews, the capsule format, whether other brands sell compatible capsules (with names), what NOT to mix and sources.

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": {
      "machine_or_capsule": "<machine_or_capsule>"
    },
    "name": "capsule_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
machine_or_capsuleYesThe machine model, system or capsule, e.g. «Essenza Mini», «Vertuo Pop», «Genio S Plus», «cápsulas L'OR», «Tassimo».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds meaningful context beyond that by enumerating what comes back — brewing method, capsule format, named third-party compatibles, incompatible combinations, and sources — which matters because no output schema exists.

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?

A single dense sentence front-loads the core question, then the system list, then the return payload. The system enumeration is long but each entry carries real scoping information rather than 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?

For a two-parameter, closed-world lookup tool with no output schema, the description covers scope, the systems handled, and the shape of the answer including sources. An agent has everything needed to decide to call it and what to expect back.

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%, with both parameters documented including the language enum and its Spanish default, so the schema does the heavy lifting. The description adds no parameter-level meaning and never mentions the language switch, so baseline 3 applies.

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?

The description opens with a specific question-shaped purpose ("Which capsules fit which machine") and enumerates the systems covered, so the resource is unambiguous. It stops short of explicitly differentiating from near neighbors such as brew_guide, especially since it also promises "how the system brews," which sounds like brew_guide's territory.

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 only implied: an agent can infer this is the tool for capsule/machine compatibility questions. There is no explicit when-to-use/when-not statement and no routing to alternatives like brew_guide or recommend_coffee_machine, leaving overlap with siblings unresolved.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources