Skip to main content
Glama

getecoback-climate-weather

daikin_laufrollensatz_anleitung_zur_wegfrage

Read-only

Prüft ob eine konkrete Frage zur vorgesehenen Bewegungsstrecke in der Teileanleitung überhaupt erfasst ist — Locate a route-specific requirement in the actual caster instructions.

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": {
      "strecke": "<strecke>",
      "dokument": "<dokument>",
      "eigenschaft_genannt": "<eigenschaft_genannt>"
    },
    "name": "daikin_laufrollensatz_anleitung_zur_wegfrage"
  }
}

Input Schema

NameRequiredDescriptionDefault
streckeYesOffene Eigenschaft der vorgesehenen Strecke.
dokumentYesZur Strecke vorliegende Quelle.
eigenschaft_genanntYesDie konkret gefragte Eigenschaft ist in der exakten Teileanleitung beschrieben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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. What the description does not disclose is the actual mechanism: whether the tool reads the manual and evaluates coverage, or merely echoes/validates the caller-supplied 'eigenschaft_genannt' boolean. That ambiguity is behavioural and material, and the description does nothing to resolve it.

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?

It is short and front-loads the condition, but the German/English pairing is not a translation of the same claim — 'überhaupt erfasst' versus 'Locate' — so the second clause adds confusion rather than precision. Two clauses where one coherent sentence would serve better.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Three required parameters, two enums, no output schema, and a semantic that is genuinely non-obvious (the caller supplies a boolean that appears to be the very answer being checked). For that complexity the description leaves the return behaviour and the role of eigenschaft_genannt unexplained, which is more than a minor gap.

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% with two enumerated parameters, so the schema carries the burden and a baseline 3 applies. The description mentions the movement path ('Bewegungsstrecke') and the manual, loosely mapping to strecke and dokument, but adds no syntax, no meaning for the enum values, and no explanation of the boolean.

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 description names a resource (Teileanleitung / caster instructions) and a subject (a route-specific requirement of the intended movement path), so the domain is identifiable. But the two halves pull in different directions: 'Prüft ob ... überhaupt erfasst ist' describes a coverage check, while 'Locate a route-specific requirement' describes retrieval. The agent cannot tell from this alone whether the tool finds the passage or simply reports whether one exists.

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 many closely named siblings (e.g. daikin_mc80zvm_rollensatz_teilcode_abgrenzen, daikin_rollenangebot_satz_und_einzelangabe_abgleichen). No preconditions, no exclusions, no alternative named. The agent must infer usage from the name.

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