Skip to main content
Glama

getecoback-raumklima

brita_maxtra_kanne_eingangswasser_quellenrahmen

Read-only

Eine gefüllte Kanne anhand der tatsächlich bestätigten Eingangswasserart dem Handbuch zuordnen — Check documented feed-water scope without evaluating quality.

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_mit_verlinkter_anleitung": "<kanne_mit_verlinkter_anleitung>",
      "ursprung": "<ursprung>",
      "temperaturhinweis": "<temperaturhinweis>",
      "beleg_von_befuellung": "<beleg_von_befuellung>"
    },
    "name": "brita_maxtra_kanne_eingangswasser_quellenrahmen"
  }
}

Input Schema

NameRequiredDescriptionDefault
ursprungYesTatsächliche Herkunft dieser einzelnen Füllung.
temperaturhinweisYesZustand beim Befüllen.
beleg_von_befuellungYesSind die Angaben für diese Befüllung und nicht nur die Küche insgesamt bekannt?
kanne_mit_verlinkter_anleitungYesIst die genaue MAXTRA PRO Kannenanleitung für diese Kombination bestätigt?

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. The description usefully adds a scope boundary ("without evaluating quality") but does not say what the mapping result looks like or what happens when the confirmed source falls outside the documented scope. Minor tension: "zuordnen" reads like an assignment while annotations say read-only, though a classification reading resolves it.

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?

One short sentence pair, front-loaded with the action and followed by the scope check. The German/English duplication is slightly redundant and mixes languages, but it costs little and the English half sharpens the intent.

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?

All four required parameters are well described and read-only behavior is annotated, so the call itself is safe to make. For a decision-producing lookup with no output schema, the description never says what the mapping yields (in-scope vs out-of-scope, manual reference), leaving an agent to discover the result shape empirically.

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 each of the four parameters is documented with enums, so the baseline is 3. The phrase "tatsächlich bestätigten Eingangswasserart" loosely echoes ursprung and beleg_von_befuellung but adds no format or decision rules beyond the schema text.

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+resource pair ("eine gefüllte Kanne ... dem Handbuch zuordnen") and qualifies it by the confirmed feed-water type, so an agent knows this is a scope-lookup rather than a quality test. It is distinguishable from siblings like brita_microdisc_haertezweck_vs_maxtra_kanne, though the vague coinage "Quellenrahmen" does not add precision.

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?

Usage is only implied: the agent is told to work from "tatsächlich bestätigten" water type and that the tool does not evaluate quality, which is a partial exclusion. There is no explicit statement of when to pick this over the sibling cartridge/water-type tools, nor any prerequisite for the confirmation evidence.

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