Skip to main content
Glama

getecoback-climate-weather

tuer_bodenberuehrung_bewegungsphase_ort

Read-only

Ordnet bereits beobachtete Bodenberührung in getrennten Öffnungs- und Schließphasen einer normalen Tür zu. — Record where already observed contact occurred while opening or closing an ordinary door.

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": {
      "oeffnen": "<oeffnen>",
      "schliessen": "<schliessen>"
    },
    "name": "tuer_bodenberuehrung_bewegungsphase_ort"
  }
}

Input Schema

NameRequiredDescriptionDefault
oeffnenYesBeobachtete Berührung beim Öffnen.
schliessenYesBeobachtete Berührung beim Schließen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety and scope are covered. The description adds that the tool handles only ordinary doors and separates opening from closing phases, but it does not explain the response or how the enum values are interpreted. It adds some context beyond annotations, but not rich behavioral detail.

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, front-loaded with the German statement and an English translation. The bilingual duplication is slightly redundant, but the definition remains tight and easy to scan.

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?

For a simple two-enum, read-only classification tool with no output schema, the description plus schema is mostly sufficient. It could be stronger if it clarified the meaning of enum values such as 'offen' or described the result of the assignment, but the core task is understandable.

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?

With 100% schema description coverage and two enum parameters, the schema already documents that each parameter is the observed contact during opening or closing. The description reinforces the opening/closing split but does not add syntax, enum meanings, or default behavior.

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 ('ordnet ... zu' / 'record') and resource ('Bodenberührung') and scopes it to separate opening and closing phases of an ordinary door. It is clear what is being assigned, though it does not explicitly contrast with any sibling tool.

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 'bereits beobachtete' signals the tool is for contact that has already been observed, not for making new observations, which is a useful usage constraint. However, it gives no explicit when-not conditions or named alternatives among the many door-related siblings.

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