Skip to main content
Glama

getecoback-raumklima

handbrause_halter_sitz_kopf_und_griff_beobachten

Read-only

Am vorhandenen Handstück Durchlass, Sitzposition und Griffzugang getrennt erfassen — Keep nozzle seating evidence separate from an accessible grip.

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": {
      "gleiche_brause_und_halter": "<gleiche_brause_und_halter>",
      "griff_passiert": "<griff_passiert>",
      "sitz_erfasst": "<sitz_erfasst>",
      "griff_greifbar": "<griff_greifbar>"
    },
    "name": "handbrause_halter_sitz_kopf_und_griff_beobachten"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitz_erfasstYesDas Handstück nimmt die tatsächlich beobachtete vorgesehene Position ein.
griff_greifbarYesAn der vorgesehenen Position kann die Person den Griff wie gewohnt erreichen.
griff_passiertYesDer beobachtete Griff gelangt ohne aufgezwungenen Druck in die vorgesehene Halterposition.
gleiche_brause_und_halterYesBeobachtung war mit derselben Brause und demselben Halter.

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 safety is covered. The description's main added value is the evidence-integrity instruction to keep seating evidence separate from grip accessibility, which is a real behavioral constraint beyond the annotations. It says nothing about what happens when an observation cannot be made, or whether partial recording is permitted.

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 short clauses, with the contextual qualifier ('am vorhandenen Handstück') front-loaded before the recording instruction. The German and English halves are largely duplicative rather than additive, but nothing is padded or buried.

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 single-observation recorder with four fully documented required fields and no output schema, the description covers the core intent and the separation principle. It leaves open whether all four fields must be captured in one call and what a recorded verdict is used for, which is a moderate remaining 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 all four parameters documented and enums on three, so the schema carries the semantic load and a baseline 3 applies. The description's 'Durchlass' plausibly maps to griff_passiert and 'Griffzugang' to griff_greifbar, but it adds no syntax, precedence, or edge-case meaning beyond the per-field text.

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 a verb (erfassen/record) and a resource (Handstück seating, grip access), but the phrasing is dense German jargon and the English half restates only two aspects, dropping the 'Durchlass' dimension. It also gives no signal distinguishing it from very similar siblings such as duschgriff_blickverdeckung_und_tatsaechliche_erreichbarkeit or duschhalter_kontaktumfang_skizze_und_produktmass. An agent grasps the general intent but not the exact scope relative to the catalog.

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 guidance, no prerequisites, and no named alternative. 'Am vorhandenen Handstück' implies a pre-existing fixture context, and 'getrennt erfassen' tells the agent to keep evidence separate, but that is an evidence-recording rule rather than guidance on when to pick this tool over its many shower/holder siblings.

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