Skip to main content
Glama

getecoback-raumklima

stadler_peter_p018_stufenvergleich_altangebot

Read-only

Erkenne bei einem alten Peter-Angebot eine widersprüchliche Stufenzahl gegenüber der aktuellen P-018-Quelle — Spot a fan speed-count mismatch against the current P-018 listing

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": {
      "typ": "<typ>",
      "messquelle": "<messquelle>",
      "anzahl_stufen": "<anzahl_stufen>",
      "anzahl_direkt_belegt": "<anzahl_direkt_belegt>"
    },
    "name": "stadler_peter_p018_stufenvergleich_altangebot"
  }
}

Input Schema

NameRequiredDescriptionDefault
typYesAuf Gerät oder Modellunterlage bestätigter Typ
messquelleYesWoher stammt die Stufenzahl?
anzahl_stufenYesGenannte oder beobachtete Anzahl der Stufen
anzahl_direkt_belegtYesDie Zahl bezieht sich auf feste Leistungsstufen ohne zusätzliche Modi

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 the safety profile is covered. The description adds that the operation is a cross-source comparison ('gegenüber der aktuellen P-018-Quelle'), but with no output schema it never says what the result looks like — a boolean mismatch flag, a diff, or a report — which is the main behavioral gap.

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, short, front-loaded statement with the core comparison condition stated first. It is somewhat redundant because the German and English halves say the same thing, but no sentence is wasted on filler.

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-parameter, read-only analysis tool with no output schema, the definition covers the input side adequately via the schema but leaves the return value and mismatch criteria unexplained. An agent knows what to send but not what to expect 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% and all four parameters carry enum values or descriptions, so the baseline is 3. The description only echoes 'Stufenzahl' (anzahl_stufen) and the two comparison sources without adding format, tolerance, or interpretation guidance for anzahl_direkt_belegt.

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 (Erkenne/Spot) and a precise object: a contradictory Stufenzahl in an old Peter offer compared against the current P-018 source. An agent can tell this is a comparison/detection task rather than a plain lookup, though it never names a sibling so the boundary against adjacent P-018 tools is left implicit.

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 scenario (an old offer whose step count must be checked against the current P-018 listing), but there is no explicit when-to-use, when-not-to-use, or named alternative for cases where no mismatch should be reported. The agent must infer the trigger condition.

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