Skip to main content
Glama

getecoback-raumklima

brita_flow_fester_standort_nachfuellen_und_zapfen

Read-only

Bei BRITA Flow ruhende Stationsmaße und praktischen Zugang zu Schiebedeckel und Zapfhahn getrennt prüfen — Identify access limits when the station body fits.

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": {
      "flow_1061561_belegt": "<flow_1061561_belegt>",
      "lichte_stellbreite_mm": "<lichte_stellbreite_mm>",
      "lichte_stellhoehe_mm": "<lichte_stellhoehe_mm>",
      "lichte_stelltiefe_mm": "<lichte_stelltiefe_mm>",
      "deckelweg_beobachtet": "<deckelweg_beobachtet>",
      "zapfen_beobachtet": "<zapfen_beobachtet>"
    },
    "name": "brita_flow_fester_standort_nachfuellen_und_zapfen"
  }
}

Input Schema

NameRequiredDescriptionDefault
zapfen_beobachtetYesIst der Zapfhahn mit eigenem Gefäß in der vorgesehenen Stellung zugänglich?
flow_1061561_belegtYesIst die BRITA Flow Artikelnummer 1061561 bestätigt?
deckelweg_beobachtetYesSind Schiebedeckel und Nachfüllen in dieser Stellung zugänglich?
lichte_stellhoehe_mmYesFreie Höhe des ruhenden Geräts, in mm.
lichte_stelltiefe_mmYesFreie Tiefe in mm.
lichte_stellbreite_mmYesFreie Breite in dokumentierter Ausrichtung, in mm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description does add a decision rule — that access limits are identified only when the station body fits — and that the two aspects are evaluated independently, which is real behavioral context. It still omits what happens with 'abweichend' or 'offen' observations and what the result looks like.

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?

It is a single sentence, which is appropriately short, and the core scope is front-loaded. The German-then-English construction restates rather than elaborates, so the second half adds little, and the compressed noun stacking makes it slower to parse than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a read-only tool requiring six mandatory inputs with no output schema, so the description is the only place an agent could learn what comes back — and it does not say. Given the complexity of six required parameters and the absence of a return-value definition, an agent cannot predict the result of the call from this definition.

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 all six parameters (including the three clearance measurements and the two enum observations) are already fully documented in the schema. The description gestures at the same concepts ('Stationsmaße', 'Zugang zu Schiebedeckel und Zapfhahn') but adds no interpretation, thresholds, or units beyond what the schema supplies, so the baseline 3 applies.

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 names the resource (BRITA Flow station dimensions plus access to the sliding lid and tap) and the action ('getrennt prüfen'), so the general intent is graspable. However, the phrasing is dense jargon ('ruhende Stationsmaße', 'Identify access limits when the station body fits') and it never states what the tool actually produces or decides. It also does nothing to separate it from the many sibling BRITA tools.

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 statement, no prerequisites, and no named alternative among the siblings. The only implied guidance is 'getrennt prüfen', suggesting dimensions and access should be assessed separately, which is a hint about internal structure rather than about when to select this tool.

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