Skip to main content
Glama

getecoback-raumklima

spueler_salzbehaelter_erstbefuellung_nachfuellen

Read-only

Wasserhinweis bei erster Salzfüllung vom Nachfüllen unterscheiden — Separate the documented first-fill water instruction from the refill case.

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>",
      "fall": "<fall>"
    },
    "name": "spueler_salzbehaelter_erstbefuellung_nachfuellen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fallYesBelegte Vorgeschichte des Geräts.
modellYesGenaues Modell aus den deutschen Unterlagen.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds the conceptual distinction it enforces but says nothing about what the caller receives back (a classification, a recommendation, a warning) or what happens when anleitung_bestaetigt is false, which matters for a decision tool with no output schema.

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?

Very short and front-loaded, with the German statement followed immediately by its English gloss. The bilingual restatement is mildly redundant, but nothing is padded and the core distinction arrives in the first clause.

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 three-parameter, fully described, read-only classification tool the description is adequate on intent, but with no output schema it leaves the return value and the consequences of each 'fall' value unexplained. An agent knows what the tool decides but not what it will get 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% and both enums are documented inline, so the schema carries parameter meaning. The description adds no interpretation of 'fall', 'modell' or the confirmation flag beyond what the field descriptions already state; 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 names the exact decision the tool performs: separating the documented first-fill water instruction from the refill case. That is a specific, actionable purpose rather than a restatement of the name, though it never distinguishes itself from neighbouring salt/rinse-aid tools such as spueler_salzprodukt_etikett_geraetemodell or spueler_salz_klarspueler_reiniger_fachbeleg.

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 it should be called when a water-filling instruction must be classified as first fill versus refill. There is no explicit when-to-use trigger, no exclusion, and no mention of the 'vorgeschichte_offen' situation where the tool is presumably still valid.

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