Skip to main content
Glama

getecoback-climate-weather

philips_na35x_rundform_durchmesser_quellenluecke

Read-only

Bei einer runden Form die getrennte Höhe aus der FAQ mit der noch offenen Durchmesserangabe abgleichen — Keep a usable height reference when the round-dish size needs separate verification.

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": {
      "geraet": "<geraet>",
      "korb": "<korb>",
      "hoehe_mm": "<hoehe_mm>",
      "aussendurchmesser_mm": "<aussendurchmesser_mm>",
      "beide_masse_gemessen": "<beide_masse_gemessen>",
      "durchmesser_eigenquelle": "<durchmesser_eigenquelle>"
    },
    "name": "philips_na35x_rundform_durchmesser_quellenluecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
korbYesIdentifizierter Korb.
geraetYesBelegte Modellfamilie des genauen Geräts.
hoehe_mmYesGemessene Außenhöhe der Form einschließlich ihrer unlösbaren Aufbauten.
aussendurchmesser_mmYesGemessener größter Außendurchmesser der Form.
beide_masse_gemessenYesSind beide Maße genau an dieser runden Form kalten Zustands gemessen?
durchmesser_eigenquelleYesLiegt für genau diesen Korb und die runde Form eine separat klare, tatsächlich lesbare Herstellerquelle vor?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 description needn't prove safety. It nevertheless adds nothing behavioral: it does not say whether a result is merely recorded, whether conflicting `durchmesser_eigenquelle` values block the comparison, or how the two measurements are reconciled. "Abgleichen" is generic and gives no operational detail.

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 and front-loads the scenario, so nothing is padded. However, the German sentence and the English sentence restate roughly the same idea rather than each adding information, and the vagueness means the brevity buys little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six required parameters, no output schema, and a domain that clearly involves measurement provenance, the description should explain the intended outcome of the comparison. It leaves unaddressed how enum values like "offen" or "abweichend" should be handled and what a successful call establishes.

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 six fully documented parameters including three enums, so the schema already carries the semantics and a baseline 3 applies. The description mentions the height reference and the open diameter value in prose but adds no constraints, formats, or interaction rules beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a resource (a round form's separate height from the FAQ plus an open diameter specification) and an action ("abgleichen"), which is more than a restatement of the name. But the phrasing is abstract and bilingual, and it never states what the tool actually returns or how it differs from the similarly named siblings about baskets, frames, and original parts.

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?

The clause "when the round-dish size needs separate verification" is a weak situational cue, not real routing guidance. There is no statement of when to use this instead of the sibling verification tools, no prerequisites, and no indication of what to do when both height and diameter are already confirmed.

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