Skip to main content
Glama

getecoback-raumklima

geraeteservice_fehlerbild_gleiche_stufe_pruefkarte

Read-only

Erfasse, wo ein gemeldeter Fehler nach Gerätepflege unter denselben dokumentierten Laststufen wieder sichtbar ist — Map a recurring climate-device issue to matched test stages

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": {
      "stufe_niedrig_vorher": "<stufe_niedrig_vorher>",
      "stufe_hoch_vorher": "<stufe_hoch_vorher>",
      "stufe_niedrig_nachher": "<stufe_niedrig_nachher>",
      "stufe_hoch_nachher": "<stufe_hoch_nachher>",
      "prueflast_aehnlich": "<prueflast_aehnlich>"
    },
    "name": "geraeteservice_fehlerbild_gleiche_stufe_pruefkarte"
  }
}

Input Schema

NameRequiredDescriptionDefault
stufe_hoch_vorherYesBeschriebenes Verhalten vor Pflege auf der höheren Stufe beobachtet
prueflast_aehnlichYesAufstellung, Gerätemodus, Testdauer und Belastung entsprechen der vorherigen Beobachtung
stufe_hoch_nachherYesNach-Pflege-Beobachtung auf gleicher höherer Stufe
stufe_niedrig_vorherYesBeschriebenes Verhalten vor Pflege auf der niedrigen Stufe beobachtet
stufe_niedrig_nachherYesNach-Pflege-Beobachtung auf gleicher niedriger Stufe

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 domain behavior beyond that: it frames the operation as comparing pre- and post-maintenance observations at the same documented load levels. It does not clarify whether 'Erfasse' produces a stored record or a computed assessment, a mild ambiguity against readOnlyHint that is not a direct contradiction.

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?

Two short clauses with the condition (recurrence after maintenance at the same stages) front-loaded and no filler. The German/English duplication is mildly redundant and the two halves are not perfectly parallel, but the text stays compact.

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 five required inputs and no output schema, the description should convey what result the agent gets back (a verdict, a matched stage, a card entry) and it does not. It also omits how 'nicht_geprueft' stages affect the outcome, leaving a meaningful gap for a tool of this complexity.

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 five documented, required parameters and two enums, so the schema carries the parameter burden. The description only reinforces the 'same documented load stages' constraint that maps onto the stufe_* and prueflast_aehnlich fields, adding no format or value guidance beyond the schema.

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 verb (Erfasse/Map) and a resource (a fault recurring under the same documented load stages after device maintenance), so the general intent is graspable. However, the key noun 'Pruefkarte' is never explained and the two language halves say slightly different things ('where the fault is visible again' vs. 'map an issue to matched test stages'), leaving the actual deliverable ambiguous. Nothing distinguishes it from the many similarly named German sibling tasks.

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?

The phrase 'nach Gerätepflege' implies a post-maintenance context, which is the only usage signal present. There is no explicit statement of when to call this versus a sibling, no prerequisites, and no exclusion such as what to do when a stage was never tested.

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