Skip to main content
Glama

getecoback-raumklima

tuerschliesser_normale_endstellung_ereignisbeleg

Read-only

Erfasst die sichtbare Endstellung einer selbstschließenden Tür im beobachteten üblichen Ablauf. — Record the visible final position of a self-closing door during normal 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": {
      "endlage": "<endlage>",
      "fremdeinwirkung": "<fremdeinwirkung>"
    },
    "name": "tuerschliesser_normale_endstellung_ereignisbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
endlageYesSichtbares Ergebnis ohne Eingriff.
fremdeinwirkungYesGab es im dokumentierten Ablauf eine bekannte Fremdeinwirkung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 covered; 'erfasst' here reads as capturing an observation rather than mutating external state, which is consistent with that. The description adds the useful constraint that the observation is of a visible end position under normal use without external influence, but says nothing about return values or what happens if the situation is not observable.

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 sentences, front-loaded with the resource being captured, with no filler. The German/English duplication is redundant for a monolingual reader but is a deliberate bilingual convention rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, fully documented observation tool with safety annotations and no output schema, the description covers what is recorded and under what circumstances. Only the boundary against sibling event-record tools remains unaddressed.

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 coverage is 100% and both parameters carry enum values with their own descriptions, so the schema already does the heavy lifting. The description adds only marginally by reinforcing the 'visible' qualifier that maps to the endlage enum and the 'normal sequence' framing that maps to fremdeinwirkung; it gives no additional interpretation of the enum choices.

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 gives a specific verb plus resource ('Erfasst die sichtbare Endstellung einer selbstschließenden Tür') and scopes it to the observed normal sequence, so an agent knows exactly what is being captured. It does not, however, distinguish itself from sibling observation/event-record tools, so the agent must rely on the name to route between them.

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 rather than stated: 'im beobachteten üblichen Ablauf' / 'during normal use' scopes it to the standard case, hinting that deviating cases belong elsewhere, but no alternative tool is named and no exclusion is explicit. An agent can infer the situation but gets no explicit when-not 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