Skip to main content
Glama

getecoback-climate-weather

spueler_tabrest_kurzprogramm_oder_blockade

Read-only

Bei Tab-Resten Hinweise aus Programm, Fach und Reinigerzustand getrennt sammeln — Keep multiple plausible explanations for a partially dissolved dishwasher tab.

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": {
      "modell": "<modell>",
      "anleitung_bestaetigt": "<anleitung_bestaetigt>",
      "rest_nach_ende": "<rest_nach_ende>",
      "programm": "<programm>",
      "fach": "<fach>",
      "auffangschale_blockiert_b": "<auffangschale_blockiert_b>",
      "reiniger_verklumpt": "<reiniger_verklumpt>"
    },
    "name": "spueler_tabrest_kurzprogramm_oder_blockade"
  }
}

Input Schema

NameRequiredDescriptionDefault
fachYesTatsächlich beobachteter Zustand von Reinigerfach und Deckel.
modellYesGenaues Modell aus den deutschen Unterlagen.
programmYesTatsächlich gelaufener und belegter Programmtyp.
rest_nach_endeYesTab-Rest nach dokumentiert beendetem Programm beobachtet?
reiniger_verklumptYesSchon vor einem Bosch-Lauf sichtbar verklumpter oder lange gelagerter Tab?
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?
auffangschale_blockiert_bYesNur bei SBV4EBX00D: Tab-Auffangschale am exakten Gerät dokumentiert und durch Geschirr versperrt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description must carry the reasoning behavior — and it does: it tells the agent to gather hints source-by-source and deliberately retain several competing explanations rather than commit. That is real behavioral guidance beyond the annotations. It does not say what form the collected evidence comes back in, so it is not fully transparent.

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 front-loaded sentence names the sources first and the goal second, with no filler. The German original plus English gloss is somewhat duplicative but aids disambiguation of a very domain-specific term.

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?

With seven required parameters and no output schema, the description should say something about what the agent receives back (a set of retained hypotheses, per-source findings). The stated intent covers the input side well but leaves the return shape entirely implicit.

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 enum and boolean semantics are already fully documented; baseline is 3. The description's grouping into Programm, Fach and Reinigerzustand does add a useful mental model, but it omits the model field and the SBV4EBX00D-only gating on the blocked-catch-tray flag.

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?

States a concrete action (collect evidence on tab remnants, split by source: program, compartment, detergent condition) plus the framing goal of keeping multiple plausible explanations. The verb+resource is specific and the differential-diagnosis framing distinguishes it from the many measurement/inspection siblings. It never names an alternative sibling, so it stops short of 5.

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: it applies when a partially dissolved tab is observed and the cause is ambiguous, and 'Keep multiple plausible explanations' implies do not collapse to one cause prematurely. There is no explicit when-not guidance, no mention of what to do if the cause is already proven, and no routing to sibling diagnostic tools.

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