Skip to main content
Glama

getecoback-raumklima

spueler_technische_unterlage_e_nummer_suffix_pruefen

Read-only

Beim vorhandenen Gerät Grundmodell, Variantenindex und Dokumentversion getrennt als Beleg prüfen — Resolve whether a primary installation drawing really belongs to the installed service variant.

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": {
      "grundmodell_gleich": "<grundmodell_gleich>",
      "index_sichtbar": "<index_sichtbar>",
      "index_in_unterlage_gleich": "<index_in_unterlage_gleich>",
      "dokumenttyp_montage": "<dokumenttyp_montage>"
    },
    "name": "spueler_technische_unterlage_e_nummer_suffix_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
index_sichtbarYesVariantenindex auf dem Typenschild ablesbar?
grundmodell_gleichYesGrundmodell in Unterlage und Typenschild gleich?
dokumenttyp_montageYesHandelt es sich um die Montagezeichnung anstelle einer allgemeinen Bedienungsanleitung?
index_in_unterlage_gleichYesIst die Unterlage dem vollständigen Index durch die Hersteller-Service-Seite zugeordnet?

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 that the check is done "getrennt als Beleg", i.e. each fact is evaluated on its own as evidence, which is useful behavioural context, but it says nothing about how a verdict is formed, what happens when a boolean is false, or what the caller gets back — relevant since there is 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?

A single dense sentence plus an em-dash gloss, with the object of the check front-loaded. Nothing is repeated and it reads quickly, but the German/English duplication of the same statement spends words without adding information.

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 predicate tool with no output schema, the description should say what the composite result means or how the booleans combine into a decision; it does not. The inputs themselves are fully covered by the schema, so the gap is limited to the outcome semantics of the check.

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 every one of the four booleans is already documented in the schema; the baseline of 3 applies. The description loosely maps its nouns onto the parameters (Grundmodell, Variantenindex, Montagezeichnung), but it adds no interpretation rules such as what combination of false values invalidates the document.

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 verification task: resolve whether a primary installation drawing belongs to the installed service variant, checking base model, variant index and document version separately as evidence. That is specific enough to separate it from neighbours like spueler_frontart_geteilt_oder_einteilig_belege or spueler_sockel_zeichnung_bezugskante_zuordnen, though the name and the mixed German/English phrasing make the object of the check slightly opaque at first read.

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 implied by the phrase "Beim vorhandenen Gerät … als Beleg prüfen", which suggests it applies when an existing unit's documentation must be evidenced. There is no explicit when-to-use trigger, no prerequisites, and no statement of which sibling to pick when the question is about a different document type (e.g. general operating instructions), so the agent must infer the boundary.

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