Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_dokumentierter_zubehoerwechsel_vor_test

Read-only

Prüfen, ob ein Lauf das mitverkaufte Zubehör oder nur ein später entferntes Teil zeigt — Match a demonstration run to the accessories that would actually transfer.

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": {
      "selbes_zubehoer_am_lauf": "<selbes_zubehoer_am_lauf>",
      "altteil_mitgegeben": "<altteil_mitgegeben>",
      "teilwechsel_nach_lauf": "<teilwechsel_nach_lauf>",
      "nachtest_mit_ersatz": "<nachtest_mit_ersatz>"
    },
    "name": "gebrauchtgeraet_dokumentierter_zubehoerwechsel_vor_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
altteil_mitgegebenYesWird das Zubehör aus der Vorführung ausdrücklich mit übergeben?
nachtest_mit_ersatzYesGibt es einen eindeutig zugeordneten Nachtest mit dem tatsächlich mitgegebenen Ersatz?
teilwechsel_nach_laufYesIst ein Wechsel des gezeigten Teils nach dem Lauf dokumentiert?
selbes_zubehoer_am_laufYesWar im gezeigten Lauf nachweislich genau das für die Übergabe vorgesehene Zubehör verbaut?

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; the description adds little beyond restating the check's subject. It never says whether the call returns a verdict, a flag, or a message, nor what happens when the four booleans contradict each other, which is the one behavior an agent would actually need here.

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-loaded, but the German sentence and the English sentence are two restatements of the same idea rather than one precise statement, so about half the text is redundant.

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?

This is a rule-evaluation tool with four required booleans and no output schema, so the description is the only place that could explain what the result means (pass/fail, which condition dominates). It omits that entirely, leaving the return value and decision semantics undocumented.

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?

With 100% schema description coverage and only four self-explanatory booleans, the schema carries the parameter meaning and the baseline 3 applies. The description gestures at the accessory-vs-removed-part distinction that maps to altteil_mitgegeben and teilwechsel_nach_lauf, but gives no decision logic or required combination.

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 does state a specific check ('Prüfen, ob ein Lauf das mitverkaufte Zubehör oder nur ein später entferntes Teil zeigt'), but the German and English halves drift apart in meaning ('match a demonstration run to the accessories that would actually transfer' reads as a matching task, not a check), and nothing distinguishes this from the many gebrauchtgeraet_* siblings that also evaluate demo evidence.

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 when-to-use guidance, no precondition, and no pointer to any alternative among the ~30 listed siblings. The agent must guess whether this is the right validation rule for a given demo-run situation.

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