Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_ausstattung_geaendertes_angebot_version

Read-only

Zwei bestätigte Angebotsfassungen auf inzwischen weggefallenes entscheidendes Zubehör abgleichen — Detect material reductions in the latest recorded used-device offer.

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": {
      "gleiches_angebot": "<gleiches_angebot>",
      "vorher_relevant": "<vorher_relevant>",
      "weiterhin_explizit": "<weiterhin_explizit>",
      "entfall_explizit": "<entfall_explizit>"
    },
    "name": "gebrauchtgeraet_ausstattung_geaendertes_angebot_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_relevantYesFür den eigenen Zweck notwendige Positionen der früheren Fassung.
entfall_explizitYesWeitere davon aktuell ausdrücklich ausgeschlossen.
gleiches_angebotYesSind beide Fassungen demselben Exemplar und Anbieter zugeordnet?
weiterhin_explizitYesDavon in der aktuellen Fassung erneut ausdrücklich enthalten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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. The description is consistent with that (a pure comparison, no mutation) but adds no further behavior: it never says what the comparison yields, whether a threshold determines 'material', or what shape the answer takes.

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?

The definition is short, but it says the same thing twice: a German clause and then an English restatement ('detect material reductions…'). The bilingual duplication consumes half the text without adding information, and the ambiguous tool name 'version' is never unpacked.

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?

With no output schema, the description would need to explain what the result means (a boolean flag, a classification, a count?), and it does not. For a compact four-parameter arithmetic comparison that is a modest but real gap; the inputs are otherwise well-covered by the schema.

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%, with each of the four parameters documented (earlier relevant positions, currently still explicitly included, newly excluded, same-offer flag). The description adds no meaning beyond that, so the baseline 3 applies — the schema carries the semantics entirely.

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: comparing two confirmed offer versions and detecting accessories that were previously essential but are now dropped. That is a specific verb+resource framing an agent can act on. It does not, however, distinguish this tool from near-neighbours such as gebrauchtgeraet_dokumentierter_zubehoerwechsel_vor_test or gebrauchtgeraet_mehrfachbeigabe_ohne_gebrauchsnachweis, which also deal with accessory changes.

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?

'Zwei bestätigte Angebotsfassungen' implies a precondition (both versions confirmed and tied to the same device/seller), which the gleiches_angebot parameter reinforces. Beyond that there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool. Usage is only inferable from the verb 'abgleichen'.

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