Skip to main content
Glama

getecoback-climate-weather

saugwischer_handbuch_ace_xt_abgleichen

Read-only

F25 XT, die referenzierte ACE-Anleitung und andere F25-Varianten für einen konkreten Beleg auseinanderhalten — Distinguish the exact F25 XT variant from the related ACE manual and other trims.

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": {
      "angebot": "<angebot>",
      "quelle": "<quelle>",
      "behauptung": "<behauptung>"
    },
    "name": "saugwischer_handbuch_ace_xt_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
quelleYesBeleg, den du für die konkrete Aussage vorliegen hast.
angebotYesVollständig gelesene Modellvariante im Angebot.
behauptungYesWorum geht es?

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 by structured data and the description only needs to add domain context, which the F25 XT vs. ACE vs. other trims scope does. The notable gap is the return behavior: with no output schema, the description should say what the classification yields (e.g. whether the Beleg is valid for the claim), and it does not.

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 front-loaded sentence with the distinguishing scope stated first, followed by an English rendering that helps with the domain terminology. The German/English duplication is mild redundancy but each version is short and the whole definition is free of padding.

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 three-required-enum, closed-domain classification tool with no output schema, the definition explains the subject matter but not the result an agent will receive or how to act on it. The parameter side is complete via the schema; the outcome side is the missing half.

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 three parameters are fully enumerated with descriptions, so the schema carries the parameter burden. The description contributes only the framing idea of a 'konkreter Beleg' mapped to the quelle parameter and adds no guidance on how to choose between enum values such as 'referenzierte_ace_anleitung' versus 'allgemeine_f25_angabe'. Baseline 3 is appropriate.

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 concrete operation (auseinanderhalten / distinguish) over specific resources: the F25 XT variant, the referenced ACE manual, and other F25 trims, scoped to a single Beleg. An agent can tell this is a disambiguation/classification tool rather than a lookup or a settings tool. It does not, however, state the outcome (a verdict on whether the source applies) or how it differs from adjacent siblings such as saugwischer_ersatzwalze_artikelabgleich.

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?

The phrase 'für einen konkreten Beleg' implies the usage context: use it when a specific document must be checked against the offer's trim. There is no explicit when-to-use/when-not-to-use rule and no sibling is named as the alternative path, so the agent must infer the trigger condition from the parameter set.

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