Skip to main content
Glama

getecoback-climate-weather

brita_kartusche_namenswechsel_altbestand_abgleichen

Read-only

BRITA MAXTRA PRO ALL-IN-1 als Vorgänger von PURE PERFORMANCE vor dem Nachkauf erkennen — Identify an officially listed predecessor without copying its capacity claim.

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": {
      "aufdruck": "<aufdruck>",
      "originalbeleg": "<originalbeleg>",
      "nachkauf_typ": "<nachkauf_typ>"
    },
    "name": "brita_kartusche_namenswechsel_altbestand_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufdruckYesEindeutig abgelesene Kennung.
nachkauf_typYesEindeutige Bezeichnung des erwogenen Nachkaufs.
originalbelegYesLiegt die tatsächlich zugehörige BRITA Originalverpackung oder ein gleichwertiger Herstellerbeleg vor?

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 adds the substantive constraint that the predecessor is "officially listed" and that its capacity claim must not be carried over — a real behavioural rule beyond the annotations. It does not, however, say what the comparison yields (a verdict, a flag, a matched entry) despite there being 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loaded with the model names, which is good. However, the German sentence and the English sentence say essentially the same thing, making roughly half the text redundant rather than additive.

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 three-required-parameter, read-only adjudication tool with no output schema, the description conveys the decision context adequately but never indicates the form of the response. An agent knows when to call it yet not what it will receive, which for a verdict-style tool is a noticeable gap.

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 two enum-typed parameters and per-field German descriptions, so the schema carries the parameter burden. The description only loosely ties the three inputs together (read-off label, intended repurchase, original proof) and adds no extra meaning such as how an "andere_oder_offen" reading should be treated.

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 verb ("erkennen"/identify) and a concrete resource (BRITA MAXTRA PRO ALL-IN-1 as predecessor of PURE PERFORMANCE) in a repurchase context, so an agent can tell it is a variant-identification check. It stops short of differentiating itself from the many neighbouring brita_* tools (e.g. kartuschenvariante_haertedaten_lesen), and the trailing clause about the capacity claim is cryptic rather than clarifying.

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?

"vor dem Nachkauf" gives a usable timing cue: call this before deciding on a replacement cartridge. There is no explicit when-not guidance, no named alternative sibling, and no statement of what to do when the reading is ambiguous (the schema's "andere_oder_offen" enum value hints at this but the description never addresses it).

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