Skip to main content
Glama

getecoback-raumklima

spuelmaschine_warmzulauf_freigabe

Read-only

Dokumentierte Warmwasser-Zulauffreigabe und Obergrenze eines Geschirrspülers prüfen — Check the exact appliance manual for permission and a maximum warm inlet temperature.

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_exakt": "<anleitung_exakt>",
      "warm_zulaessig": "<warm_zulaessig>",
      "maximum_c": "<maximum_c>",
      "zulauf_c": "<zulauf_c>"
    },
    "name": "spuelmaschine_warmzulauf_freigabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
zulauf_cYesBeobachtete höchste Zulauftemperatur in Grad Celsius.
maximum_cYesDokumentierte obere Zulauftemperatur in Grad Celsius; bei fehlender Angabe 0.
warm_zulaessigYesIst Warmwasseranschluss laut dieser Anleitung ausdrücklich zulässig?
anleitung_exaktYesGilt die Anleitung für die genaue Modellvariante?

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 the closed-world scope are covered; the mention of checking the 'exact appliance manual' is consistent with that. However, the description never says what the tool returns (a verdict? a comparison?) and there is no output schema, so the agent must guess the response shape.

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 sentence with the verification target front-loaded, followed by the source constraint. The German/English duplication is somewhat redundant but each version carries the full meaning, so there is no real 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?

With four required parameters, no output schema, and minimal annotations, the definition covers the inputs adequately via the schema but leaves the result semantics undefined — an agent cannot tell whether it gets a boolean verdict, a comparison of observed vs. documented temperature, or a message.

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 four parameters are already documented in the schema, including the fallback convention that maximum_c is 0 when absent. The description only restates the concepts already present (exact manual, maximum inlet temperature) and adds no syntax or edge-case meaning beyond the schema.

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 a specific verb ('prüfen' / check) and a specific resource pair: the documented warm-water inlet permission and the upper temperature limit of a dishwasher. It is clearly narrower than a generic appliance lookup, though it does not name a sibling or explicitly contrast with the other '_freigabe' tools.

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: the phrase 'Check the exact appliance manual' signals that this tool is for source-bound verification against a specific manual rather than general advice. There is no explicit when-to-use/when-not statement and no named alternative among the many sibling '_freigabe' 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