Skip to main content
Glama

getecoback-climate-weather

beurer_ks34_milliliter_fluid_unze_anzeigemodus

Read-only

Bei KS 34 70311 das Gewichtsfeld oz oder lb:oz von einer gewünschten Flüssigkeits-Volumeneinheit unterscheiden — Check whether the desired volume unit is actually supported.

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>",
      "einheit": "<einheit>"
    },
    "name": "beurer_ks34_milliliter_fluid_unze_anzeigemodus"
  }
}

Input Schema

NameRequiredDescriptionDefault
einheitYesGesuchte Einheit.
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.3/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 genuine context by framing this as a support/feasibility check rather than a setting change, hinting that some volume units may not be available. It says nothing about what the check returns or how uncertainty ('unklar') is reported.

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?

It is short, but the German sentence and the English gloss say essentially the same thing, so roughly half the text is redundant. The device constraint is front-loaded, which is good, but the duplication costs conciseness.

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 verification tool with no output schema, the description should say what the result expresses (e.g. supported vs. unsupported unit) and how the boolean gate interacts with the answer. It covers the question being answered but leaves the response shape entirely implicit.

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 'einheit' enum plus the 'modell_belegt' boolean are both documented in the schema. The description mentions the desired fluid-volume unit, matching 'einheit', but adds no syntax, defaults, or guidance on how 'modell_belegt=false' should be supplied. Baseline 3 applies since the schema carries the semantics.

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 device (KS 34 70311) and a concrete operation: distinguishing the weight field 'oz'/'lb:oz' from a requested fluid-volume unit, i.e. verifying unit support. That is a specific verb+resource, far from a tautology of the tool name. It stops short of naming a sibling it is not, so it lands 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?

The clause 'Check whether the desired volume unit is actually supported' implies the situation (a user asking for ml/fl_oz display) but never states when to use this versus the many adjacent KS 34 clarification tools. No explicit exclusions or prerequisites are given, so usage must be inferred.

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