Skip to main content
Glama

getecoback-climate-weather

beurer_ks34_artikelnummer_wiegeoberflaeche

Read-only

Wiegefläche der Beurer KS 34 nach deutscher Artikelnummer 70311 oder 70312 zuordnen — Resolve the documented contact surface from the exact German variant.

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": {
      "nummer": "<nummer>",
      "nachweis": "<nachweis>"
    },
    "name": "beurer_ks34_artikelnummer_wiegeoberflaeche"
  }
}

Input Schema

NameRequiredDescriptionDefault
nummerYesVom Typenschild oder Angebot eindeutig zugeordnete Artikelnummer.
nachweisYesOriginalhersteller oder Typenschild ist 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, and the word 'documented' is consistent with that closed-world, read-only profile. The description adds little beyond this — it does not say what is returned when 'nummer' is 'unklar' or what the 'nachweis' flag changes about the result.

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, but the German sentence and its English restatement convey the same information twice, so roughly half the text is redundant rather than additive. It is front-loaded and wastes no space on preamble, which keeps it serviceable.

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 lookup with no output schema, the description covers the core mapping adequately. It leaves two gaps the agent must guess at: the meaning of the ambiguous 'unklar' input and the role of the required 'nachweis' proof flag.

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 the schema already documents both parameters and the enum values. The description reinforces the article-number constraint ('exact German variant') but adds nothing about how the 'nachweis' boolean affects the resolution.

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 (zuordnen / 'Resolve') tied to a specific resource (Wiegefläche / 'contact surface') and scopes it to the exact German article numbers 70311/70312. An agent can tell this apart from related siblings like wiegebereich_fuenf_gramm_und_einteilung, though no sibling is named explicitly.

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 only implied: 'from the exact German variant' signals the tool applies when a precise article number is known, and the enum's 'unklar' option hints at an ambiguity path, but there is no explicit when-to-use/when-not statement or pointer to an alternative tool.

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