Skip to main content
Glama

getecoback-raumklima

beurer_lb55_kalkpad_packungswiderspruch

Read-only

Lies die konkrete Packungsstückzahl des dokumentierten LB-55-Kalkpads — Read the actual pack quantity for the documented LB 55 scale pad

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_68605": "<modell_68605>",
      "zubehoer_163141": "<zubehoer_163141>",
      "stueckzahl_belegt": "<stueckzahl_belegt>",
      "packungsmenge": "<packungsmenge>"
    },
    "name": "beurer_lb55_kalkpad_packungswiderspruch"
  }
}

Input Schema

NameRequiredDescriptionDefault
modell_68605YesLB-55-Geräteartikel 68605 am Typenschild identifiziert
packungsmengeYesStückzahl auf der Packung, 0 wenn nicht bekannt
zubehoer_163141YesAngebot zeigt Kalkpad-Artikel 163141
stueckzahl_belegtYesStückzahl am konkreten Packungsaufdruck belegt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 the safety profile is covered. The description adds no behavioral context beyond the annotations: it does not say what happens when the quantity is unproven (stueckzahl_belegt=false) or unknown (packungsmenge=0), nor how the 'contradiction' implied by the name is resolved.

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?

Very short and front-loaded, but the German and English sentences are verbatim duplicates rather than complementary, so half the text is redundant. No structural cues (e.g., what to do on a mismatch) are provided.

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 read-only, closed-world tool with a fully documented four-parameter schema and no output schema, the description is minimally adequate. It is incomplete regarding the decision logic the name advertises — how to interpret a pack quantity that is not backed by the printed packaging — which is the tool's apparent reason for existing.

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% with four required, well-documented parameters, so the schema carries the semantics. The description adds no meaning about the parameters or how the boolean evidence flags interact with the reported quantity; baseline 3 applies.

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?

States a specific verb and resource: 'Lies die konkrete Packungsstückzahl des dokumentierten LB-55-Kalkpads' / 'Read the actual pack quantity for the documented LB 55 scale pad'. An agent knows exactly what is retrieved, but nothing distinguishes it from the many other LB-55/Beurer sibling tools, and the name's 'Packungswiderspruch' (packaging contradiction) framing is never explained in the description.

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?

No when-to-use guidance, no prerequisites, and no named alternative among the large sibling set. The agent must infer from the name alone that this is the tool for resolving a pack-quantity discrepancy rather than, say, a general spec lookup.

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