Skip to main content
Glama

getecoback-climate-weather

brita_maxtra_pro_kartuschenvariante_haertedaten_lesen

Read-only

PURE PERFORMANCE und EXTRA KALKSCHUTZ nur mit örtlich belegter Härteklasse und persönlichem Zweck einordnen — Match manufacturer positioning without inferring reduction.

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": {
      "haerteklasse": "<haerteklasse>",
      "bericht_zum_anschluss": "<bericht_zum_anschluss>",
      "zweck": "<zweck>"
    },
    "name": "brita_maxtra_pro_kartuschenvariante_haertedaten_lesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
zweckYesGewünschter Vergleichszweck.
haerteklasseYesSo bezeichnet der örtliche Versorger die Härte für den konkreten Anschluss.
bericht_zum_anschlussYesIst der Härtebereich dem vorhandenen Anschluss und aktuellen Versorgungsdaten zugeordnet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 useful domain constraints (require locally evidenced hardness data, avoid inferring reduction effects), but it does not describe what the response contains or how classification is expressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

It is short but front-loaded with slogan capitalization ('PURE PERFORMANCE und EXTRA KALKSCHUTZ') that conveys no callable meaning, pushing the one substantive constraint to the end of the sentence. Space that could clarify the operation is spent on marketing language.

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?

With a fully documented 3-parameter schema, annotations, and no output schema, the description needs only to state the operation and its guardrails. The guardrails are present, but the core operation remains ambiguous, which leaves the definition only marginally sufficient for correct invocation.

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 coverage is 100% with enum descriptions for zweck and haerteklasse, so the schema already carries parameter meaning. The description only lightly echoes this by tying 'örtlich belegte Härteklasse' and 'persönlicher Zweck' together, adding no format or interpretation detail beyond the schema.

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 says to 'einordnen' (classify) something against a locally documented hardness class and a personal purpose, which hints at a read/assessment operation, but it never plainly states what data is read or returned. The marketing lead-in 'PURE PERFORMANCE und EXTRA KALKSCHUTZ' obscures the actual verb+resource pairing, and no sibling is named for differentiation.

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?

It gives a real gating condition — only use when the hardness class is locally documented and a personal purpose exists — plus a prohibition against inferring reduction ('without inferring reduction'). However, it does not name an alternative tool or say when a different sibling should be used instead, so routing is left to inference.

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