Skip to main content
Glama

getecoback-raumklima

tuerzugang_griff_manoevrieren_passage_getrennt

Read-only

Hält für einen bereits beobachteten persönlichen Türdurchgang Griffzugang, Manövrieren und Passage getrennt fest. — Record handle reach, manoeuvring and passage separately for an already observed door use.

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": {
      "griff": "<griff>",
      "manoever": "<manoever>",
      "passage": "<passage>"
    },
    "name": "tuerzugang_griff_manoevrieren_passage_getrennt"
  }
}

Input Schema

NameRequiredDescriptionDefault
griffYesKonnte die betreffende Person in der dokumentierten Nutzung zum Griff gelangen?
passageYesGelang der dokumentierte Durchgang mit der verwendeten Unterstützung?
manoeverYesWar die benötigte Bewegung vor oder hinter der Tür in dieser Beobachtung möglich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, but the description uses a write verb ('festhalten' / 'Record'), implying an observation is persisted somewhere. The description does not resolve this tension: it never says whether data is stored, appended to a prior record, or merely structured and returned for an already-observed case, which is exactly the behaviour an agent needs to know. The contradiction is milder than a plain create/read mismatch (the values arrive as input parameters), but it remains an unresolved conflict.

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 compact sentences with the recorded aspects front-loaded and the 'already observed' constraint trailing. The German and English are duplicated, which adds length without new information, but there is otherwise no filler.

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 only three required enum parameters and no output schema, the definition needs to convey purpose and precondition, which it does. What it omits is the fate of the data and the relationship to sibling separation tools, leaving an agent unable to predict the effect of calling it.

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 all three parameters carry German question-form descriptions plus ja/nein/offen enums, so the schema does the semantic heavy lifting. The description restates the three aspect names but adds no interpretation of what 'offen' means in practice or how the three aspects relate, leaving it at the baseline.

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 and object: it records three named aspects (handle reach, manoeuvring, passage) separately for one door use, so an agent knows precisely what the tool captures. It stops short of distinguishing itself from the many sibling '*_getrennt' tools, which share the 'recorded separately' framing.

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 'for an already observed door use' is a useful precondition: the observation must exist already, this tool does not perform the observation. There is no when-not guidance, no exclusions, and no pointer to any alternative for a door use that has not yet been observed, so the boundary must be inferred.

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