Skip to main content
Glama

getecoback-raumklima

daikin_mc80zvm_griffrolle_zweck_und_fundstelle

Read-only

Leitet für das genaue Modell von einer gewünschten Bewegungsart zur passenden Quellenstelle — Route carrying and optional rolling to their own manufacturer documentation.

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": {
      "vorhaben": "<vorhaben>",
      "fundstelle": "<fundstelle>",
      "modell_passt": "<modell_passt>"
    },
    "name": "daikin_mc80zvm_griffrolle_zweck_und_fundstelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorhabenYesBeschriebene Bewegungsart.
fundstelleYesVorliegender Beleg.
modell_passtYesDie Unterlage gilt für das deutsche MC80ZVM.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/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 covered by structured data. The description adds no behavioral context of its own: it does not say what a 'Quellenstelle' answer looks like, whether the 'offen' enum values mean 'no result', or how conflicting inputs (modell_passt=false) are handled.

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?

One sentence keeps it short and front-loads the routing action, but the second half is a redundant English gloss of the first rather than new information. Brevity here is closer to under-specification than to disciplined concision.

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 three required enum parameters and no output schema, the description should at minimum explain what the tool returns and how the 'offen' fallbacks resolve; it only gestures at 'passende Quellenstelle'. It is adequate for a small read-only lookup but leaves a real gap around return semantics and edge cases.

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 coverage is 100% with two documented enums, so the schema already carries the parameter burden. The description marginally reinforces two of them ('gewünschte Bewegungsart' → vorhaben, 'für das genaue Modell' → modell_passt) but adds no interpretation the schema lacks, such as what each 'offen' value implies. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Leitet ... zur passenden Quellenstelle' plus the scoping phrase 'für das genaue Modell' conveys a mapping/lookup operation from motion type to a source document. However, 'Quellenstelle' is never defined, and the trailing English clause ('Route carrying and optional rolling to their own manufacturer documentation') is a loose paraphrase rather than a sharper statement. An agent gets the gist but not a crisp, unambiguous purpose.

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 or when-not-to-use guidance and no alternative named, despite siblings such as daikin_laufrollensatz_anleitung_zur_wegfrage and daikin_mc80zvm_rollensatz_teilcode_abgrenzen that appear closely related. The only implicit hint is 'für das genaue Modell', which does not tell the agent how to choose between this tool and its neighbours.

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