Skip to main content
Glama

getecoback-climate-weather

dachfenster_hitzeschutz_typabgleich

Read-only

Das geplante Dachfenster-Zubehör anhand der schriftlichen Typzuordnung überprüfen — Match roof-window shade documentation to the exact existing window type.

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": {
      "kennzeichnung_ablesbar": "<kennzeichnung_ablesbar>",
      "modellcode_gelistet": "<modellcode_gelistet>",
      "oeffnungsart_bestaetigt": "<oeffnungsart_bestaetigt>",
      "bestandszubehoer_geprueft": "<bestandszubehoer_geprueft>"
    },
    "name": "dachfenster_hitzeschutz_typabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellcode_gelistetYesFührt die Zubehörunterlage diesen exakten Fenster- und Größencode auf?
kennzeichnung_ablesbarYesLässt sich die vollständige Fensterkennzeichnung inklusive Größen- und Typcode ablesen?
oeffnungsart_bestaetigtYesIst die Öffnungsart für diese Kombination dokumentiert?
bestandszubehoer_geprueftYesIst vorhandenes Zubehör laut Produktunterlagen zur Kombination geeignet oder keines vorhanden?

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, and the description is consistent with a non-mutating check. It adds real context beyond the annotations — the check is against *schriftliche* (written) type assignment and must match the *exakten* existing window type — but it never says what a false booleans produces or how a mismatch is surfaced.

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?

One front-loaded German sentence plus a short English gloss — efficient and readable for a bilingual audience, with no filler. The English half is a loose paraphrase rather than a translation ('shade documentation' vs. accessory check), which costs a little precision but not length.

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 four-required-boolean verification tool with no output schema, the definition covers what is being verified but not what the agent receives or how to interpret an all-true vs. mixed result. Given the annotations already carry the safety profile, this is adequate but leaves the outcome semantics to inference.

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 the four booleans are already precisely glossed in the schema (Kennzeichnung ablesbar, Modellcode gelistet, Öffnungsart bestätigt, Bestandszubehör geprüft). The description adds no syntax, ordering, or dependency detail beyond that, so the 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 a specific verb (überprüfen/match) and a specific resource (geplantes Dachfenster-Zubehör vs. schriftliche Typzuordnung des bestenden Fensters), so the agent knows this is a documentation-to-reality type check, not a calculation or a lookup. It does not differentiate itself from any named sibling, but the purpose itself is unambiguous.

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?

There is no when-to-use guidance: nothing says this is a pre-order/pre-install check, no alternatives are named, and no conditions (e.g. what to do when a booleans comes back false) are stated. The only implicit signal is the word 'geplantes', which a reader must infer means 'before commitment'.

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