Skip to main content
Glama

getecoback-raumklima

betriebszustand_uhr_passive_anzeige_getrennt

Read-only

Eine sichtbare Uhr auf einen belegten Bezug zur Stromversorgung des Geräts prüfen — Separate independent analogue movement or retained display from a mains-powered clock function.

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": {
      "sichtbare_uhr": "<sichtbare_uhr>",
      "anzeigeart": "<anzeigeart>",
      "bezug_belegt": "<bezug_belegt>"
    },
    "name": "betriebszustand_uhr_passive_anzeige_getrennt"
  }
}

Input Schema

NameRequiredDescriptionDefault
anzeigeartYesEnergiebezug der tatsächlichen Anzeige laut exakter Geräteunterlage.
bezug_belegtYesQuelle oder vollständige Erklärung gilt für diese konkrete Anzeige, nicht nur für die Gerätefamilie?
sichtbare_uhrYesWar im abgegrenzten Beobachtungsfenster eine Uhr sichtbar?

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 the safe-read profile is covered. The description adds the conceptual distinction being tested, but does not explain what happens when evidence is missing, how 'offen' is handled, or what the verification result looks like.

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?

A single sentence, but it is written twice — once in German and once in English — with the two halves partially non-equivalent (the English drops the 'belegt' evidence requirement). The duplication adds length without adding information.

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 3-required-parameter read-only classification tool with no output schema, the description covers the intent but leaves the result shape and the treatment of the 'offen' enum value unexplained. Adequate to attempt a call, thin for interpreting the outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and every parameter carries its own description plus an enum for 'anzeigeart', so the schema does the heavy lifting. The description's 'belegten Bezug' wording reinforces that evidence must apply to this concrete display rather than the device family, giving a mild boost over baseline 3.

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?

States a specific act — verifying whether a visible clock has a documented link to the device's power supply — and frames the distinction (independent analogue movement / retained display vs. mains-powered clock function). It is not a tautology of the name and the check target is understandable, but it never says what the tool returns or how it differs from the many sibling 'getrennt' tools.

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?

No explicit when-to-use, when-not, or named alternative. The dash clause implies the scope (separating an independent movement from mains-powered operation), and the boolean 'bezug_belegt' parameter hints the check only applies when evidence exists, so usage is inferable but never stated.

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