Skip to main content
Glama

GATA Cafeteras

Descaling and cleaning guide

maintenance_guide
Read-onlyIdempotent

How often and how to descale and clean a coffee machine by brand (De'Longhi, Philips/Saeco, Nespresso, Dolce Gusto, Tassimo, Siemens, SENSEO, Melitta, Sage, Bialetti and any brand added later), which descaler to use and step-by-step instructions, from the manufacturers' manuals, with sources. Error codes and broken parts are redirected to GATA Recambios.

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": "<machine>"
    },
    "name": "maintenance_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
machineYesBrand and/or model, e.g. «De'Longhi Magnifica S», «Philips 2200 LatteGo», «Nespresso Vertuo».
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
questionNoThe user's question, e.g. «se ha encendido la luz naranja» or «error E3».

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 declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavioral context beyond them: answers are drawn from manufacturers' manuals and come 'with sources', and out-of-scope topics (error codes, broken parts) are routed elsewhere. It does not say what the response shape looks like, but the sourcing claim is meaningful.

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?

Purpose is front-loaded in the first clause, and the redirect note sits at the end where it functions as a scope boundary. The long brand enumeration is somewhat bulky but serves a matching purpose; otherwise there is little waste.

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

Completeness3/5

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

For a 3-parameter read-only tool with full schema coverage and no output schema, the description covers scope, sources and brand range adequately. The one real gap is the conflict between the stated redirect of error-code questions and the schema examples that invite exactly those questions, which an agent cannot resolve from the definition alone.

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%, so the baseline is 3 and the schema already explains machine, language and question with examples. The description adds only the brand coverage list ('and any brand added later'), which mildly extends the meaning of 'machine' but not enough to raise it above baseline.

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 concrete verb-plus-resource statement ('How often and how to descale and clean a coffee machine by brand') and enumerates scope (descaler selection, step-by-step instructions, manuals with sources). It does not name any sibling (e.g. brew_guide) for the drinking/brewing side, so differentiation from siblings is only implied by the descaling/cleaning framing.

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

Usage Guidelines4/5

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

It states clearly what the tool answers (frequency, descaler choice, procedure) and gives an explicit exclusion: 'Error codes and broken parts are redirected to GATA Recambios.' However, that exclusion is undercut by the schema's own example question 'error E3' and 'se ha encendido la luz naranja', leaving the boundary for error/indicator-light questions ambiguous.

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