Skip to main content
Glama

getecoback-raumklima

beurer_ks34_halteanzeige_protokollspeicher_unterschied

Read-only

Hold-Anzeige am Gerät und einen für spätere Nutzung gespeicherten Messwert unterscheiden — Check whether a visible held reading can satisfy a history requirement.

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>",
      "bedarf": "<bedarf>"
    },
    "name": "beurer_ks34_halteanzeige_protokollspeicher_unterschied"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedarfYesWas soll mit der Messung passieren?
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 agent knows nothing is mutated and no external system is touched; the description is consistent with that. It adds modest value by making clear this is a distinction/verification question rather than a device action, but gives no insight into what the answer looks like, how the three 'bedarf' cases resolve, or how model uncertainty affects the conclusion.

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 clauses, front-loaded with the core distinction and followed by the decision framing; nothing is padded. The German and English halves partially restate each other, which costs a little, but the English clause genuinely adds the check framing.

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 two-parameter, read-only advisory tool with full schema coverage and no output schema, the description covers the essentials of what is being distinguished. It is still incomplete on the outcome logic — what conclusion follows when the model is not verified or the need is 'unklar' — which for a decision tool is the part an agent would actually need.

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 both parameters carry their own descriptions and an enum, so the schema does the heavy lifting — baseline 3 applies. The description adds no extra meaning: it never explains why confirming the German KS 34 XL Black 70311 variant ('modell_belegt') is required or how 'unklar' should be handled relative to the other enum values.

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 names a concrete distinction pair — the 'Halte-Anzeige' on the device versus a measurement value stored for later retrieval — and adds the decision framing ('Check whether a visible held reading can satisfy a history requirement'). An agent can tell this is a conceptual/advisory distinction tool rather than a device operation. It stops short of naming a sibling, but the purpose itself is specific.

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 by the second clause: use this when someone needs to know whether a held reading counts as stored history. There is no explicit when-not guidance, no mention of the 'modell_belegt' dependency (that the answer may hinge on confirming the KS 34 XL Black 70311 variant), and no routing to related tools for the actual storage or measurement behavior.

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