Skip to main content
Glama

getecoback-climate-weather

spuelgang_ende_marker_und_autoopen_beobachtung

Read-only

Das gelesene Ende-Zeichen und die beobachtete Türbewegung getrennt als Laufbelege führen — Distinguish a program completion marker from a door event.

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": {
      "passende_anleitung": "<passende_anleitung>",
      "ende_text_gelesen": "<ende_text_gelesen>",
      "tuer_automatisch_beobachtet": "<tuer_automatisch_beobachtet>",
      "restzeit_beim_oeffnen": "<restzeit_beim_oeffnen>"
    },
    "name": "spuelgang_ende_marker_und_autoopen_beobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_text_gelesenYesEnde wurde an diesem Lauf tatsächlich gelesen.
passende_anleitungYesDer beobachtete Ende-Text ist in der passenden Herstelleranleitung ausdrücklich als Programmende belegt.
restzeit_beim_oeffnenYesAnzeige bei beobachteter Türbewegung.
tuer_automatisch_beobachtetYesAutomatische Türbewegung an diesem Lauf unabhängig beobachtet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive read-only operation with an openWorldHint of false. The description adds that the end marker and door movement should be kept separately as run evidence, but it does not disclose validation behavior, error conditions, or what makes a record acceptable beyond the schema.

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?

The definition is a single compact sentence with the key distinction front-loaded, followed by an English clarification. The bilingual repetition is slightly redundant but does not obscure the intent.

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 read-only record tool with four fully described required parameters and no output schema, the definition is minimally adequate. It does not explain how this tool relates to the many sibling observation tools, which is the main contextual gap.

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%, so all four required parameters and the enum values are already documented in the schema. The description reinforces the separation between the end marker and door event but adds no syntax, format, or interpretation details beyond the schema.

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 states a specific operation: separately recording the read end marker and the observed door movement as run evidence, and distinguishing a program completion marker from a door event. The purpose is clear, though it does not differentiate this tool from the many similarly named observation siblings.

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 guidance on when to use this tool, when not to use it, or which sibling tools cover adjacent observation cases. The description implies it is for recording two distinct observations, but an agent must infer the operational context.

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