Skip to main content
Glama

getecoback-raumklima

luftkuehler_pflegedokument_tank_matte_unterscheiden

Read-only

Prüft ob die Unterlagen Tankentnahme und Pflege der konkreten Matte getrennt beschreiben — Verify model-specific and separate care instructions for the reservoir and evaporative pad.

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_eindeutig": "<modell_eindeutig>",
      "tank_beschrieben": "<tank_beschrieben>",
      "matte": "<matte>"
    },
    "name": "luftkuehler_pflegedokument_tank_matte_unterscheiden"
  }
}

Input Schema

NameRequiredDescriptionDefault
matteYesDie konkrete Matte laut Anleitung.
modell_eindeutigYesExaktes Modell und passende Handbuchausgabe liegen vor.
tank_beschriebenYesDie Anleitung beschreibt Behandlung und Entnahme des Tanks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 known and the description only needs to add substance. It does add that the verification covers separation of the two topics plus model specificity, but it never says what the verdict looks like or how the three input states map to a result, and there is no output schema to fill that gap.

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 stating the check condition, with the German/English pairing kept parallel. Slight duplication from bilingualism, but no filler and nothing that could be trimmed without losing the statement.

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?

Three required parameters and full schema coverage keep the burden low, but with no output schema the description should say what the tool returns for a check of this kind (a verdict, a list of missing documentation, etc.). The relationship between the input flags — which already assert documentation state — and the returned result remains unstated.

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 schema already documents all three parameters and the enum values, giving a baseline of 3. The description adds the conceptual frame (separate, model-specific care instructions) but no extra syntax, format, or interpretation detail 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?

Names a specific verb ('Prüft / Verify') and a specific object: whether the documents describe tank removal and care of the concrete mat separately and model-specifically. An agent can tell this is a documentation-verification check rather than a measurement or setup tool. It stops short of naming any sibling, but the verb+resource pairing is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this versus the many other luftkuehler_* checks, and no prerequisites or exclusions. The only hint is that it applies when care documentation is being reviewed, which the agent must infer from 'Unterlagen'.

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