Skip to main content
Glama

getecoback-raumklima

lb200_ziellicht_betriebshinweis

Read-only

Lies beim Beurer LB 200 die Anzeige ohne leuchtenden Zielwert richtig — Interpret the Beurer LB 200 with no target light

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": {
      "geraeteartikel_10069": "<geraeteartikel_10069>",
      "dauert_betrieb_an": "<dauert_betrieb_an>",
      "licht": "<licht>"
    },
    "name": "lb200_ziellicht_betriebshinweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
lichtYesWelcher Zielwert leuchtet?
dauert_betrieb_anYesGerät ist laut Anzeige/Beobachtung weiterhin im normalen Betrieb
geraeteartikel_10069YesDie Typkennzeichnung bestätigt Beurer LB 200, Geräteartikel 10069

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so this is a safe, closed-world read. The description adds no behavior beyond that — no explanation of what a 'kein_zielwert' or 'unklar' reading implies, no indication of what the call returns, and no error or ambiguity handling.

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?

The definition is short and front-loaded, but it is a bilingual restatement of the same sentence in German and English, which duplicates rather than adds information. No structural waste beyond that redundancy.

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

Completeness2/5

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

There is no output schema, so the description is the only place that could explain what an 'interpretation' returns, and it does not. For a diagnostic tool with three required inputs and no return documentation, the agent is left guessing the result format.

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% and the enum values are documented in the schema, so the schema carries the parameter semantics. The description adds no meaning about the three inputs, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific device (Beurer LB 200) and a specific condition (display with no lit target value), and the verbs 'Lies ... richtig' / 'Interpret' point at a diagnostic reading task. But the verb phrase is vague — it is not obvious whether the tool reads a sensor, classifies a fault, or answers a question — and nothing distinguishes it from the many other Beurer/LB200 diagnostic 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 explicit when-to-use or when-not-to-use guidance and no named alternative. The scenario 'display without a lit target value' is implicit in the description, which is the only cue an agent has for selecting this tool over siblings such as beurer_lb200_filter_frist_auslastung.

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