Skip to main content
Glama

getecoback-raumklima

duschkabinentuer_brausenablage_einstieg_ausstieg

Read-only

Bei einem vorhandenen Halter erforderliche Türstellung und freie Beweglichkeit für Ein- und Ausstieg getrennt protokollieren — Distinguish arrival and exit observations around the same shower screen.

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": {
      "einstieg_frei": "<einstieg_frei>",
      "ausstieg_frei": "<ausstieg_frei>",
      "festgesetzte_tuerstellung": "<festgesetzte_tuerstellung>",
      "gleiche_ablage": "<gleiche_ablage>"
    },
    "name": "duschkabinentuer_brausenablage_einstieg_ausstieg"
  }
}

Input Schema

NameRequiredDescriptionDefault
ausstieg_freiYesDer übliche Ausstieg war nach unabhängiger Beobachtung frei.
einstieg_freiYesDer übliche Einstieg war mit derselben vorgesehenen Türstellung und abgestellter Handbrause beobachtet frei.
gleiche_ablageYesHalter, Handbrause und Schlauchlage waren in beiden Beobachtungen gleich.
festgesetzte_tuerstellungYesBeide Beobachtungen gehören zur wirksam beobachteten tatsächlichen Türstellung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior1/5

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

The description says 'getrennt protokollieren', which implies recording or persisting observations, while the annotations declare readOnlyHint=true. This is a direct contradiction about whether the tool mutates state. Beyond the contradiction, it does not explain what is recorded, where, or what the result contains.

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?

The description is short and front-loads the core action and scope. The English gloss is somewhat redundant but helpful for disambiguation, and there is no unnecessary padding.

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?

For a four-parameter required-input tool with no output schema, the description leaves important gaps. It does not explain what 'protokollieren' returns or how the recorded observations are represented, and the read-only annotation contradiction makes the tool's behavioral contract unclear.

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 input schema already defines all four parameters in detail, including enum values and boolean meanings. The description adds useful framing that the observations concern the same shower screen and distinguish entry from exit, but it does not add meaning beyond what the schema provides for individual parameters.

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 states a specific action (getrennt protokollieren) and resource (Türstellung und freie Beweglichkeit für Ein- und Ausstieg) and adds the precondition of an existing holder. It clearly separates entry and exit observations, though it does not explicitly differentiate itself from sibling tools.

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?

The phrase 'Bei einem vorhandenen Halter' gives a precondition for use, implying this tool applies when a holder is already present. However, it does not say when to use this versus alternatives or when not to use it.

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