Skip to main content
Glama

getecoback-raumklima

brita_maxtra_pro_rueckgabe_uebergabe_quittung

Read-only

Bei der Kartuschenrückgabe Zusage und tatsächliche Übergabe getrennt halten — Track confirmed recycling handoff without inventing acceptance.

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": {
      "originale_pro_geprueft": "<originale_pro_geprueft>",
      "gesammelte_einheiten": "<gesammelte_einheiten>",
      "abgabepunkt_aktuell_bestaetigt": "<abgabepunkt_aktuell_bestaetigt>",
      "quittierte_einheiten": "<quittierte_einheiten>",
      "einheiten_beim_haushalt": "<einheiten_beim_haushalt>"
    },
    "name": "brita_maxtra_pro_rueckgabe_uebergabe_quittung"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesammelte_einheitenYesEindeutig identifizierte gebrauchte Einheiten im betrachteten Vorgang.
quittierte_einheitenYesTatsächlich als übergeben quittierte Einheiten.
originale_pro_geprueftYesSind die gezählten gebrauchten Einheiten als BRITA MAXTRA PRO bestätigt?
einheiten_beim_haushaltYesSeparat nachweislich weiterhin zu Hause erfasste Einheiten.
abgabepunkt_aktuell_bestaetigtYesIst ein tatsächlich akzeptierender deutscher Abgabepunkt oder Rücksendeweg bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 contributes one real behavioral constraint — it will not treat unconfirmed units as accepted ('without inventing acceptance') — but says nothing about the result shape or how the confirmed handoff is reported, which matters because there is no output schema.

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?

A single short sentence with the core constraint front-loaded and no filler. It is efficient, though the abstraction of 'Track' leaves the reader working to reconstruct the concrete action.

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?

For a five-required-parameter, read-only evaluation tool with no output schema and no annotations describing return values, the description should say what the call produces and how counts and booleans relate. Instead it offers only a design principle, leaving the agent unable to predict the response.

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?

All five parameters are fully documented in the schema (coverage 100%), including bounds and German-language semantics for each count and boolean. The description adds no parameter-level meaning beyond this, so the baseline 3 applies.

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 the resource (Kartuschenrückgabe) and the principle of the operation (keeping Zusage and tatsächliche Übergabe separate), but the verb 'Track' is abstract. It never says concretely what the tool computes or returns, and it does not distinguish itself from near-name siblings such as altgeraete_abholvorgang_tatsaechliche_uebergabe or brita_maxtra_pro_wechsel_kalender_und_mengenbeleg.

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?

'Bei der Kartuschenrückgabe' gives only topical context; there is no explicit statement of when to call this versus the surrounding BRITA MAXTRA PRO tools, and no exclusions or prerequisites. The agent must infer usage entirely from the name and schema.

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