Skip to main content
Glama

getecoback-raumklima

beurer_ks34_tara_bruttolast_tragkraft

Read-only

Schüssel und Inhalt zusammen gegen die Tragkraft der Beurer KS 34 prüfen, auch wenn die Anzeige tariert ist — Count gross load against the documented limit even after tare.

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>",
      "gefaess_g": "<gefaess_g>",
      "inhalt_g": "<inhalt_g>"
    },
    "name": "beurer_ks34_tara_bruttolast_tragkraft"
  }
}

Input Schema

NameRequiredDescriptionDefault
inhalt_gYesGeplante Masse des Inhalts oder der Gesamtzutaten in Gramm.
gefaess_gYesGemessene Masse des leeren Gefäßes in Gramm.
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 safety is covered. The description adds the meaningful behavioral point that taring does not reduce the load counted against the limit (gross, not net), but says nothing about what verdict or figure is produced or what happens when the limit is exceeded.

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 core constraint is front-loaded and short, but the sentence is restated almost verbatim in a second language, which doubles length without adding information. The German half alone would carry the same content more efficiently.

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 three-required-parameter read-only check with no output schema, the description conveys the computation but not the result: it never says whether the tool returns a pass/fail verdict, a headroom figure, or the numeric limit used. That is a notable gap given the absent output schema.

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%, so all three parameters (inhalt_g, gefaess_g, modell_belegt) are already documented in the schema. The description confirms the intent that bowl and contents are summed, but adds no format, unit, or tolerance semantics beyond what the schema supplies.

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 states a concrete check: sum bowl plus contents and compare against the documented load capacity of the Beurer KS 34, explicitly noting that a tared display does not exempt the load. This is a specific verb+resource and distinguishes the tool from plain tare-handling siblings, though it does not name any sibling by name.

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?

It gives a clear usage condition ('even when the display is tared') that identifies when the agent should reach for this tool rather than a simple net-weight check. However, it never states when not to use it or points to an alternative among the many tare/gross-load siblings.

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