Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_zustandswort_mit_einzelbefund_abgleichen

Read-only

Pauschalen Angebotszustand gegen tatsächlich untersuchte Punkte abgleichen — Translate broad seller condition language into observed and open checks.

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": {
      "untersuchte_punkte": "<untersuchte_punkte>",
      "abweichungen": "<abweichungen>",
      "nur_behauptet": "<nur_behauptet>",
      "ungefragt_offen": "<ungefragt_offen>"
    },
    "name": "gebrauchtgeraet_zustandswort_mit_einzelbefund_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
abweichungenYesDavon tatsächlich abweichend von der angebotenen Zustandsbeschreibung.
nur_behauptetYesWeitere bei der Besichtigung unbestätigte Punkte, die nur der Anbieter angegeben hat.
ungefragt_offenYesWeitere für die Entscheidung nötige Punkte ohne Angabe.
untersuchte_punkteYesAnzahl der selbst oder unabhängig begutachteten einzeln bezeichneten Punkte.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 and the description need only add context. It does convey that the operation classifies points into observed versus still-open categories, but with no output schema it says nothing about what the reconciliation result contains or how deviations are weighed.

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 compact clauses with the German statement of scope front-loaded and the English gloss following as clarification; nothing is padded. The em-dash construction is efficient, though the second half is interpretive rather than operational.

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 computation over four fully documented numeric inputs, annotations and schema carry most of the weight. The remaining gap is the absent output schema combined with a description that never indicates what the agent receives back, which matters for a tool whose whole job is producing a comparison result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every one of the four required counts (untersuchte_punkte, abweichungen, nur_behauptet, ungefragt_offen) is already documented in the schema. The description's framing reinforces the conceptual split between claimed and examined points without contradicting the schema, which is all that is needed here.

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 specific action (abgleichen/reconcile) and both operands: a broad seller condition claim versus individually examined points. The English gloss ('Translate broad seller condition language into observed and open checks') makes the intent readable even without the German, though it stays slightly metaphorical rather than stating a concrete output.

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?

Usage is implied by the framing — use it when a seller offers only a blanket condition statement and you have itemised findings to compare against it. There is no explicit when-not guidance and no named alternative among the gebrauchtgeraet siblings (e.g. the photo-crop or changed-offer-version tools) is contrasted.

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