Skip to main content
Glama

getecoback-climate-weather

beurer_ks34_magic_led_schwarzes_display_beobachtung

Read-only

Dunkles Magic-LED-Display im Leerlauf und fehlende Anzeige bei einer Messung unterscheiden — Interpret the observable idle display behaviour independently of a possible fault.

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": {
      "modell_belegt": "<modell_belegt>",
      "messzustand": "<messzustand>"
    },
    "name": "beurer_ks34_magic_led_schwarzes_display_beobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
messzustandYesZeitpunkt einer dunklen Anzeige.
modell_belegtYesDie deutsche Ausführung KS 34 XL Black 70311 ist am konkreten Gerät belegt?

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 safety profile is covered. The description adds meaningful framing beyond that: the interpretation is of *observable* behaviour and must be kept separate from fault attribution, which constrains how conclusions are drawn. It does not say what is returned or how ambiguity ('unklar') is handled, so it remains a moderate score.

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 concrete display states and followed by the interpretive constraint. The German and English halves partially restate each other, which costs a little efficiency, but nothing is padded or off-topic.

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 read-only two-parameter observational tool this is mostly sufficient: scope, stance, and the two observable states are conveyed. It lacks any indication of the answer shape (no output schema exists) and does not clarify the role of modell_belegt in the interpretation, leaving a modest 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 coverage is 100% — both parameters (modell_belegt, messzustand with its enum) are documented in the schema itself. The description's distinction between idle dark display and dark display during measurement loosely maps to the messzustand enum values but adds no format, value, or edge-case detail. 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 gives a concrete verb ('unterscheiden') and a specific subject: a dark magic-LED display when idle versus no display during a measurement. It also states the interpretive stance ('independently of a possible fault'). It does not name or distinguish itself from related sibling observation tools such as betriebszustand_stichprobe_display_status_muster, so it stays at 4 rather than 5.

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: this is the tool for the situation where the display stays dark and you must decide whether that is normal idle behaviour or an actual measurement fault. There is no explicit when-not guidance and no alternative tool is named for the fault case, so an agent must infer routing from the sibling list.

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