Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_unbenutzt_behauptung_nach_zaehlerwechsel

Read-only

Bei behaupteter Nichtbenutzung prüfen, was ein zurückgesetzter oder gewechselter Zähler überhaupt belegt — Limit a zero counter reading to the documented counter history.

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": {
      "verkaeufer_sagt_unbenutzt": "<verkaeufer_sagt_unbenutzt>",
      "zaehlerstand": "<zaehlerstand>",
      "historie": "<historie>",
      "zaehler_definition_belegt": "<zaehler_definition_belegt>"
    },
    "name": "gebrauchtgeraet_unbenutzt_behauptung_nach_zaehlerwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
historieYesNachgewiesener Bezug des Zählers zum gesamten Zeitraum.
zaehlerstandYesBeobachtete Anzahl Einsätze im betreffenden Zähler.
verkaeufer_sagt_unbenutztYesBehauptet der Anbieter ausdrücklich bisher keine Benutzung?
zaehler_definition_belegtYesWurde bestätigt, dass jedes relevante Ereignis mit dieser Anzeige tatsächlich erfasst wird?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/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 genuine behavioral substance by stating the tool's epistemic stance: it limits what a zero counter reading may be taken to prove and ties it to the documented history rather than issuing a simple unused/used verdict.

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?

It is a single front-loaded sentence with the condition stated first and the constraining rule second, and nothing is filler. The German sentence is followed by an English gloss, which is mildly redundant but short enough not to be wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-required-parameter, no-output-schema assessment tool, the definition supplies the deciding logic an agent needs: the claim condition, the counter-history qualifier, and the deliberate limitation of evidence. It does not need to describe return values, and the annotations already cover the read-only profile.

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%, so every parameter including the historie enum is already documented. The description only loosely echoes two of them (zero reading, reset/swapped counter) and adds no format, threshold, or interpretation detail beyond what the schema supplies, so the baseline of 3 applies.

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 states a specific analytical task: assess what a reset or swapped counter reading actually proves when the seller claims non-use, and to limit a zero reading to the documented counter history. It is clear in domain terms but never positions itself against any sibling tool in the catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger condition ('Bei behaupteter Nichtbenutzung') plus the qualifying situation of a reset or swapped counter, which is enough for an agent to know when the tool applies. It offers no exclusions or pointers to alternative tools, which keeps it short of a 5.

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