Skip to main content
Glama

Explain an appliance error code

diagnose_error_code
Read-onlyIdempotent

Explains what an error code on a washing machine, dishwasher or tumble dryer means (Bosch/Siemens/Balay E17, E18, E23, E21, E15, E22, E24, E25, E09; Samsung 4C, 5C, UE, DC, HC, LC, dryers NC, tC, HC, dF; LG IE, OE, UE, dE, LE, FE, PE, tE, CL; AEG/Electrolux/Zanussi E10, E20, E40, E50, i10, i20, i30; Whirlpool FH, FA, FOD), likely causes, safe step-by-step checks, whether a technician is needed, the parts that usually fail with buy links and the page URL. Older aliases (F18, 4E, 5E, E1…) also work.

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": {
      "code": "<code>"
    },
    "name": "diagnose_error_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code on the display, e.g. «E18», «4C», «OE», «i20».
brandNoBrand, e.g. Bosch, Balay, Siemens, Samsung, LG, AEG, Electrolux, Zanussi, Whirlpool, Indesit, Beko, Candy, Teka.
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
applianceNoAppliance: lavadora (washing machine), lavavajillas (dishwasher), secadora, frigorifico, horno, placa, campana, microondas. Free text is fine.
model_numberNoModel number / E-Nr. / PNC if the user has it, to make part links exact.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 the safety profile is covered. The description adds genuinely new behavior: the answer includes likely causes, safe step-by-step checks, a technician-needed judgement, commonly failing parts with buy links, and the source page URL — telling the agent what to expect in the response body. It does not state rate limits or what happens for an unrecognized code, which keeps it below 5.

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?

The core purpose and deliverables are front-loaded in the first clause, and the second sentence about aliases is short and useful. The long parenthetical code enumerations are dense but earn their place by enabling direct code-to-tool matching, though they push the description close to a catalogue dump.

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

Completeness4/5

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

There is no output schema, so the description carries the burden of describing return content, and it does so thoroughly (causes, checks, technician verdict, parts with links, URL). Combined with a fully documented input schema, an agent has enough to call this correctly; only the behavior on unknown codes or brands is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all five parameters and the baseline is 3. The description nonetheless adds meaning beyond the schema by asserting that older aliases of the code format are accepted, and by listing brand/code families that clarifies what values of `brand` and `code` are actually resolvable.

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?

The description opens with a specific verb+resource ("Explains what an error code ... means") and scopes it to three appliance types with a concrete, verifiable code inventory across seven brand families. It also enumerates the deliverables (causes, safe checks, technician verdict, failing parts, page URL), which makes it unmistakable versus siblings like repair_guide or find_spare_part.

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 strongly implied: this is the tool for a code shown on an appliance display, and the alias sentence ("Older aliases (F18, 4E, 5E, E1…) also work") tells the agent it need not normalize legacy codes first. However, there is no explicit when-not or routing to alternatives such as repair_guide or find_model_number, so the agent must infer the boundary.

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