Skip to main content
Glama

getecoback-raumklima

tuer_zugluftstopper_lose_durchgangsbeobachtung

Read-only

Unterscheidet einen vorhandenen losen Zugluftstopper außerhalb des Durchgangs von beobachtetem Hindernis oder Verlagerung beim Alltagseinsatz. — Record whether a loose draught stopper stays outside the passage, moves into it or obstructs observed 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": {
      "gegenstand": "<gegenstand>",
      "beeintraechtigung": "<beeintraechtigung>"
    },
    "name": "tuer_zugluftstopper_lose_durchgangsbeobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
gegenstandYesBereits beobachtete Position im Verlauf der normalen Nutzung.
beeintraechtigungYesWar in dieser Situation der Durchgang sichtbar beeinträchtigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true, but the English description says 'Record whether...', which implies a write or persistence action. The German 'Unterscheidet' is read-only/classificatory, creating an internal inconsistency between the description and annotations. This contradiction warrants score 1 and an annotation-contradiction flag.

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?

The purpose is front-loaded, but the German and English sentences duplicate the same content and the English phrasing is not a clean translation. It is not bloated, but the bilingual restatement is redundant and could be tightened into one precise sentence.

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?

Although the schema and annotations cover the inputs and safety profile, the description does not explain the return value or what the tool outputs when given the two enum inputs. The read-only-versus-record ambiguity also leaves an important behavioral gap for an agent trying to call this correctly.

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?

The input schema has two required enum parameters with 100% description coverage, so the schema already carries the parameter meaning. The description's 'stays outside, moves into it, or obstructs observed use' roughly reflects some enum values, but it does not explain all values such as 'offen' or add syntax beyond the schema. Baseline 3 applies.

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 specific resource (loose draught stopper relative to the passage) and an observable outcome (stays outside, moves into it, or obstructs use). It is understandable without opening the schema, but it does not differentiate this tool from any sibling and the German/English wording adds slight ambiguity.

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?

Usage is implied through 'beim Alltagseinsatz' and 'observed use', suggesting this is for everyday observation of a loose draught stopper. However, there is no explicit when-to-use vs when-not guidance, no prerequisites, and no named alternative among the many sibling tools.

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