Skip to main content
Glama

getecoback-climate-weather

altgeraete_symbol_anlage_drei_weglese

Read-only

Eine beobachtete durchgestrichene Tonne vom Sammelstellen-Symbol unterscheiden — Tell a separate-collection mark from the marked route to a collection point.

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": {
      "symbol": "<symbol>",
      "ort": "<ort>",
      "beobachtung_bestaetigt": "<beobachtung_bestaetigt>"
    },
    "name": "altgeraete_symbol_anlage_drei_weglese"
  }
}

Input Schema

NameRequiredDescriptionDefault
ortYesWo befand sich die dokumentierte Kennzeichnung?
symbolYesWelches Zeichen wurde eindeutig beobachtet?
beobachtung_bestaetigtYesOrt und Zeichen sind durch eine vollständige Beobachtung eindeutig belegt?

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 safety is covered. The description adds nothing about behavior: it does not say what happens when observations are ambiguous (the 'nicht_eindeutig' enum hints at handling but is never explained), nor whether 'beobachtung_bestaetigt=false' blocks the operation or merely flags it.

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?

Very short, but the same sentence is stated twice (German then English) while the genuinely ambiguous parts — 'drei_weglese', the output, the confirm-flag semantics — go unaddressed. Space is spent duplicating rather than clarifying.

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?

With three required parameters, no output schema, and a name implying a three-way read, the description should say what the tool produces and how the discrimination resolves. It instead stops at restating the topic, leaving the agent unable to predict the result of a call.

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 enum values and per-field descriptions, so the schema carries the parameter burden and baseline 3 applies. The description adds no meaning beyond it — notably it never explains the relationship between the confirmation boolean and the observation it supposedly validates.

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 specific discrimination task — telling a crossed-out bin mark apart from a collection-point mark — which is more than a restatement of the name. But the operative verb ('unterscheiden' / 'tell ... from') leaves unclear whether the tool returns a classification, records an observation, or validates a premise, and the name's 'drei_weglese' (three-way reading) is never explained.

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 statement of when to call this versus the many other altgeraete_* siblings, and no prerequisites or exclusions. The only implicit cue is the subject matter itself; an agent must guess the triggering situation from the sibling list.

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