Skip to main content
Glama

getecoback-climate-weather

beurer_ks34_versandgewicht_unverpackt_quellenabweichung

Read-only

Verpackte Masse, aktuelle unverpackte Herstellerangabe und älteres ungefähres Datenblattgewicht unterscheiden — Keep packed and unpacked weights and source revisions separate.

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>",
      "vergleichsbezug": "<vergleichsbezug>"
    },
    "name": "beurer_ks34_versandgewicht_unverpackt_quellenabweichung"
  }
}

Input Schema

NameRequiredDescriptionDefault
modell_belegtYesDie deutsche Ausführung KS 34 XL Black 70311 ist am konkreten Gerät belegt?
vergleichsbezugYesBenötigter Gewichtsbezug.

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 safety is covered. The description adds the behavioral constraint that packed vs. unpacked and current vs. older sources must remain separate, which is real added context, but it says nothing about what the call produces or how an unresolved 'ungeklaert' case is handled.

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?

A single front-loaded sentence that states the three items to be separated before the summarizing clause. The verbatim German/English duplication is redundant but short, and no sentence is wasted.

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 low-complexity two-parameter tool with a fully described schema and no nested objects, the definition is close to adequate. However, with no output schema the description should indicate what the separation result looks like, and it does not, leaving a real gap for an agent deciding how to interpret the response.

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%, so both parameters are already documented, including the enum values for vergleichsbezug. The description reinforces the packed/unpacked distinction that maps onto that enum but adds no syntax or format meaning, and 'modell_belegt' goes unmentioned. Baseline 3 applies when the schema carries the load.

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 specific operation — keeping packed weight, current unpacked manufacturer figure, and an older approximate datasheet weight/source revision apart — rather than restating the tool name. It is a semantic-separation tool, and that intent is legible, though the description never says plainly whether it returns a classification, a warning, or just guidance.

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 stated principle: when weight figures conflict, do not collapse them. There is no explicit when-to-use trigger, no when-not condition, and no reference to sibling tools such as the tare/gross-load or weighing-range definitions, so the agent must infer the boundary itself.

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