Skip to main content
Glama

getecoback-climate-weather

wasserkocher_twk8613p_deckel_kalksieb_gebrauchsbeleg

Read-only

Prüft nach der Pflege, ob Deckel und entnehmbares Kalksieb wie vorgesehen am Bosch montiert und beobachtet sind — Confirm two documented kettle assembly conditions before use.

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": {
      "anleitung_zugeordnet": "<anleitung_zugeordnet>",
      "deckel_geschlossen": "<deckel_geschlossen>",
      "sieb_eingesetzt": "<sieb_eingesetzt>"
    },
    "name": "wasserkocher_twk8613p_deckel_kalksieb_gebrauchsbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
sieb_eingesetztYesDas zugeordnete Kalksieb wurde am Platz beobachtet.
deckel_geschlossenYesDer Deckel ist am kalten Gerät geschlossen und das wurde beobachtet.
anleitung_zugeordnetYesDas Gerät ist als deutsches TWK8613P identifiziert und die angegebene TWK86-Anleitung über die E-Nummer zugeordnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 the safety profile is covered without help. The description contributes the useful behavioral frame that this is a verification step tied to a maintenance ('Pflege') sequence, but it says nothing about what the recorded result means or what downstream action an 'offen' outcome implies. It does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, which is good, but the single sentence is stated twice in two languages and the two versions disagree on timing ('nach der Pflege' vs. 'before use'). The duplication consumes the whole budget without adding a single new constraint, so the brevity reflects under-specification rather than economy.

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-required-parameter, read-only, output-schema-less check, the description covers what is verified and roughly when, which is the minimum an agent needs. It leaves out how the result should be interpreted and how this step relates to the surrounding kettle workflow, which matters given the large sibling set.

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 all three parameters — including the belegt/ausgeschlossen/offen enums — are already documented in the schema. The description only echoes two of the three (Deckel, Kalksieb) and never mentions the identification/anleitung_zugeordnet condition. Baseline 3 applies when the schema does the explanatory work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource are present ('Prüft ... ob Deckel und entnehmbares Kalksieb ... montiert'), so an agent can tell this is an assembly-state verification for two named parts. But the phrasing is garbled ('montiert und beobachtet sind') and the sentence is split across German and English without the English half adding precision. No sibling tool is named or contrasted, so the boundary against tools like spuelmaschine_basis_kanne_sieb or the descaling tools is left implicit.

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?

Timing context is implied but internally inconsistent: the German says the check happens 'nach der Pflege' (after cleaning) while the English says 'before use'. An agent gets a rough sense of where this fits, but no explicit when-not-to-use condition and no pointer to an alternative tool if the check fails.

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