Skip to main content
Glama

getecoback-raumklima

duschhalter_greifen_zuruecklegen_bewegung_getrennt

Read-only

Eine vorgesehene Ablage auf Greifen und Zurücklegen aus der gleichen räumlichen Haltung getrennt prüfen — Keep retrieval and replacement observations distinct.

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": {
      "greifen": "<greifen>",
      "zuruecklegen": "<zuruecklegen>",
      "platzwechsel": "<platzwechsel>",
      "gleicher_ablauf": "<gleicher_ablauf>"
    },
    "name": "duschhalter_greifen_zuruecklegen_bewegung_getrennt"
  }
}

Input Schema

NameRequiredDescriptionDefault
greifenYesDie Person nimmt die Handbrause aus der vorgesehenen Position.
platzwechselYesWurde zwischen den Schritten ein Positionswechsel beobachtet?
zuruecklegenYesDie Person legt die Brause in derselben Nutzungslage zurück.
gleicher_ablaufYesWaren Zubehör, Griffstellung und betrachtete Nutzungslage gleich?

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 the safety profile is known. The description adds the semantic constraint that retrieval and replacement must be judged as distinct observations rather than merged, which is genuine context. It does not say what the tool produces or how the recorded assessment is surfaced, and no output schema exists to fill that gap.

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?

It is short and front-loads the core intent, with the English clause acting as a clarifying restatement rather than padding. The bilingual duplication is mildly redundant but does not obscure meaning.

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 fully documented in the schema and annotations cover the read-only nature, so nothing essential is missing for invocation. For a four-required-field recording tool with no output schema, though, the description should indicate what the assessment yields or how results are persisted, which it does not.

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 every enum/boolean is already explained in the schema, so the baseline is 3. The description reinforces the two core parameters (greifen, zuruecklegen) and the 'same spatial posture' idea behind gleicher_ablauf, but adds no value semantics beyond the schema 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 the resource ('Greifen und Zurücklegen aus der gleichen räumlichen Haltung') and a verb ('getrennt prüfen'), so the general intent is discernible. However 'Eine vorgesehene Ablage ... prüfen' is convoluted phrasing, and nothing in it distinguishes this tool from the many other '*_getrennt' siblings beyond the generic 'keep observations distinct' idea.

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 statement of when to use this tool versus the sibling separation tools, and no exclusions or prerequisites. The phrase 'aus der gleichen räumlichen Haltung' implies a scoping condition for the observation, but it is not framed as usage guidance.

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