Skip to main content
Glama

getecoback-climate-weather

brita_maxtra_pro_wechsel_kalender_und_mengenbeleg

Read-only

Kalender und dokumentierte Filtermenge getrennt gegen den MAXTRA PRO Herstellerhinweis lesen — Check which published replacement trigger is documented.

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": {
      "kartusche_pro_belegt": "<kartusche_pro_belegt>",
      "erste_nutzung_belegt": "<erste_nutzung_belegt>",
      "kalendertage": "<kalendertage>",
      "mengenlog_voll": "<mengenlog_voll>",
      "gefiltert_l": "<gefiltert_l>",
      "haertebezug": "<haertebezug>"
    },
    "name": "brita_maxtra_pro_wechsel_kalender_und_mengenbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
gefiltert_lYesBereits vollständig protokollierte, gefilterte Menge in Litern.
haertebezugYesZugeordnete örtliche Härte nach dem Herstellerbezug.
kalendertageYesKalendertage einschließlich Nutzungsunterbrechungen seit Erstnutzung, nicht nur Nutzungstage.
mengenlog_vollYesSind seit Erstnutzung alle durchgeflossenen Mengen dieses Exemplars zugeordnet?
erste_nutzung_belegtYesIst der Tag der ersten Nutzung dieser Kartusche bestätigt?
kartusche_pro_belegtYesIst eine originale MAXTRA PRO im Geltungsbereich der Tischkannen-Anleitung bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 that calendar and documented volume evidence are read separately and checked against the manufacturer's published trigger, but it does not explain behavior when inputs are inconsistent or incomplete, nor what the result contains.

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?

The definition is a single front-loaded sentence with no filler. It is compact and readable, though the second clause partly restates the first, which keeps it below a 5.

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 six-parameter check with full schema descriptions, the definition is mostly adequate. However, with no output schema, it should state more explicitly what the tool returns (which trigger or evidence status) and what happens if neither trigger is documented.

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 six required parameters are already documented in the schema. The description only alludes to kalendertage and the documented filtered quantity, adding no extra syntax, validation rules, or parameter interaction semantics beyond what the schema provides.

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 verb ('lesen') and the two resources being compared (Kalender and dokumentierte Filtermenge) against the MAXTRA PRO Herstellerhinweis, then says it checks which replacement trigger is documented. This is a clear evaluation task, though it does not differentiate itself by name from related Brita siblings.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named among the many Brita siblings. The phrase 'gegen den Herstellerhinweis lesen' implies a comparison context, but an agent gets no rule for choosing this tool over the mengenjournal or deckelanzeige-related 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