Skip to main content
Glama

getecoback-raumklima

daikin_mc80zvm_rollensatz_teilcode_abgrenzen

Read-only

Liest für die exakt belegte deutsche MC80ZVM-Ausführung, welcher Teilecode zu Rollen und welcher zum Filter gehört — Distinguish the exact Daikin caster kit code from the filter code.

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": {
      "teil": "<teil>",
      "ausgabe_passt": "<ausgabe_passt>"
    },
    "name": "daikin_mc80zvm_rollensatz_teilcode_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
teilYesGelesene Herstellerkennung.
ausgabe_passtYesExaktes MC80ZVM und die genannte deutsche Anleitung abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 is covered and the description does not need to restate it. In exchange it adds the real constraint that the lookup only holds for the exactly verified German MC80ZVM manual edition. It says nothing about what is returned or what happens when the code is 'andere' or 'offen', which is the behavior an agent most needs to anticipate.

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?

The German clause is front-loaded and purposeful, but the English half is a near-verbatim restatement rather than added information, effectively doubling length for zero gain. Trimming the redundant translation would make this a tight one-liner.

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 two-parameter, closed-world read tool with full schema coverage, the description is close to sufficient, but with no output schema it should say what the result is (a resolved code? a mapping? a verdict?) and how partial or ambiguous cases are signalled. As written, an agent knows the input shape but not what it will get back.

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 both parameters are already documented and the 3 baseline applies. The description adds the notion of exact-edition matching but never explains the semantics of the enum branches ('andere', 'offen') or what ausgabe_passt=true unlocks, so it contributes no new 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 pairs a concrete verb ("Liest") with a concrete resource (the Teilecode for Rollen vs. Filter for the exact German MC80ZVM variant), so an agent knows it resolves a parts-code ambiguity rather than looking something up generally. It stops short of a 5 because the cryptic enum values (kks080b41, baft501a) are never tied to 'Rolle' or 'Filter' in the prose, leaving the actual mapping implicit.

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 statement of when to call this versus the closely named siblings such as daikin_rollenangebot_satz_und_einzelangabe_abgleichen or daikin_laufrollensatz_anleitung_zur_wegfrage. The only usage cue is the implicit prerequisite 'exakt belegte deutsche Ausführung', which surfaces in the schema but not in the description as guidance.

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