Skip to main content
Glama

getecoback-raumklima

geraet_ersatz_ausloeser_fehlende_zusatzfunktion

Read-only

Bei Ersatzabsicht nachhalten, ob die entscheidende Gerätefunktion nach einer bestätigten Änderung jetzt belegt ist — Revisit a replacement trigger only for the verified missing function.

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": {
      "mangel": "<mangel>",
      "routine_beleg": "<routine_beleg>",
      "zusatz_beleg": "<zusatz_beleg>",
      "aenderung_nachweis": "<aenderung_nachweis>"
    },
    "name": "geraet_ersatz_ausloeser_fehlende_zusatzfunktion"
  }
}

Input Schema

NameRequiredDescriptionDefault
mangelYesWelcher Bedarf hat den Ersatzvergleich ausgelöst?
zusatz_belegYesStand der Zusatzfunktion nach der bestätigten Änderung.
routine_belegYesStand der Routinefunktion nach der bestätigten Änderung.
aenderung_nachweisYesSind Änderung und Ergebnis auf Ansatz und Zweck des genauen Geräts bezogen belegt?

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the check applies only after a confirmed change and is scoped to the verified missing function, but it does not describe the result or how the evidence enums are evaluated.

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?

The description is short and front-loads the replacement-intent condition before the scoping clause. The English paraphrase after the dash is mildly redundant but still compact and does not bury the key condition.

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 read-only evaluation tool with four required, fully documented parameters and no output schema, the description is adequate on inputs and preconditions. It remains incomplete about what the call returns or how the enum states translate into a replacement decision, which matters because no output schema is provided.

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% and all four parameters have descriptions, including three enums, so the schema carries parameter semantics. The description reinforces the confirmed-change and missing-function context but does not add enum meanings or explain how mangel, routine_beleg, zusatz_beleg, and aenderung_nachweis combine.

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 identifies a follow-up check on a replacement trigger for a verified missing additional function, and the 'after a confirmed change' condition narrows the purpose. However, the verb 'nachhalten' is ambiguous between tracking/recording and checking, and the definition does not distinguish this from related replacement or service-function siblings.

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?

It gives an implied usage condition: use it when there is replacement intent and only for the verified missing function. It does not state when not to use it or name any alternative sibling for broader replacement or routine-vs-additional-function cases.

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