Skip to main content
Glama

getecoback-climate-weather

brita_flow_style_gesamtvolumen_vorrat_trennen

Read-only

Gefilterte Nennkapazität vom Gesamtvolumen zweier genau dokumentierter BRITA Kannen unterscheiden — Flag purchases based on gross rather than filtered capacity.

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": {
      "kanne": "<kanne>",
      "gleichzeitig_benoetigt_l": "<gleichzeitig_benoetigt_l>",
      "anzeige_bewirbt_gesamt": "<anzeige_bewirbt_gesamt>"
    },
    "name": "brita_flow_style_gesamtvolumen_vorrat_trennen"
  }
}

Input Schema

NameRequiredDescriptionDefault
kanneYesExaktes deutsches Produkt.
anzeige_bewirbt_gesamtYesWurde im Angebot nur das Gesamtvolumen als Fassungsvermögen hervorgehoben?
gleichzeitig_benoetigt_lYesEigener Bedarf an gefilterter Menge ohne Nachfüllen, in Litern.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 and the description only needs to add context. It does note that the jugs are "genau dokumentiert" and that the outcome is a purchase flag, but with no output schema it never says what the returned flag/result actually contains or how the threshold comparison is decided.

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?

Two compact clauses, front-loaded with the core distinction followed by the practical purpose; nothing is redundant. The mixed German/English phrasing is slightly awkward but does not obscure meaning.

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, closed-world decision tool with three fully documented parameters this is close to adequate, but with no output schema the description should say what the flag/comparison result looks like. As written, an agent knows the topic but not the shape of the answer.

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 the schema already documents all three parameters, and the baseline is 3. The description's filtered-vs-gross framing loosely maps onto gleichzeitig_benoetigt_l and anzeige_bewirbt_gesamt but adds no concrete interpretation, units, or thresholds beyond what the schema states.

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 specific operation (distinguish filtered nominal capacity from total volume) on a specific resource (two precisely documented BRITA jugs), so an agent knows this is a comparison/decision task rather than a lookup. It does not name any sibling or state what makes this tool distinct from the many other BRITA tools, keeping it short of a 5.

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?

"Flag purchases based on gross rather than filtered capacity" implies the scenario (evaluating an offer that advertises gross capacity) but gives no explicit when-to-use/when-not guidance and no named alternative among the many sibling BRITA tools. Usage must be inferred from the purchase-flagging phrase.

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