Skip to main content
Glama

getecoback-climate-weather

brita_maxtra_mengenjournal_mit_zwischenstand_wechsel

Read-only

Dieselbe MAXTRA Kartusche beim Wechsel in eine andere Kanne bis zum tatsächlichen Ersatz den eigenen Litern zuordnen — Keep the same cartridge total through a jug move and stop at the next cartridge.

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": {
      "kartuschen_identitaet_belegt": "<kartuschen_identitaet_belegt>",
      "alte_kanne_l": "<alte_kanne_l>",
      "neue_kanne_davor_l": "<neue_kanne_davor_l>",
      "neue_kanne_danach_l": "<neue_kanne_danach_l>",
      "wechsel_luecke_offen": "<wechsel_luecke_offen>"
    },
    "name": "brita_maxtra_mengenjournal_mit_zwischenstand_wechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
alte_kanne_lYesVollständig gemessene Menge mit der ursprünglichen Kanne.
neue_kanne_davor_lYesVollständig gemessene Menge mit der neuen Kanne vor dem tatsächlichen Kartuschenwechsel.
neue_kanne_danach_lYesSeparat vollständig gemessene Menge der Ersatzkartusche.
wechsel_luecke_offenYesSind zusätzlich Durchläufe im Wechselintervall ohne gesicherte Zuordnung bekannt?
kartuschen_identitaet_belegtYesIst dasselbe konkrete Exemplar bis zur ausdrücklich dokumentierten Ersetzung nachvollziehbar?

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 adds genuinely useful behavioral content — the cartridge must stay the same through the jug move and the tally must stop at the actual replacement — but it never says what the call produces or how identity/gap flags affect the outcome.

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?

It is a single sentence with no filler, but the German and English halves restate the same content rather than complementing each other, and the core verb phrase ('den eigenen Litern zuordnen') is dense enough to obscure the action. Front-loading the resource (MAXTRA cartridge) is done well.

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?

Five required parameters and no output schema, so the description should at least indicate the shape of the result; it hints at a stopping rule but not at what is returned. For a read-only computation tool of this complexity, that leaves a meaningful gap, though the invocation semantics are inferable from 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% and all five parameters are individually documented, so the baseline is 3. The description echoes the underlying concepts (same cartridge, move, actual replacement) but adds no per-parameter meaning such as how 'wechsel_luecke_offen' or 'kartuschen_identitaet_belegt' alter the computed total.

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 bilingual sentence conveys the domain intent — attributing one MAXTRA cartridge's liters across a jug move until it is actually replaced — but it reads as an imperative rule rather than stating what the tool does (compute a running total? validate a journal entry?). The opaque tool name and null title mean the description carries the whole naming burden, and it only partly discharges it.

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 when-to-use/when-not phrasing and no reference to any alternative. The clause 'stop at the next cartridge' implies a boundary condition, but the agent is left to infer when this journal step applies versus the sibling calendar/quantity tools.

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