Skip to main content
Glama

getecoback-raumklima

philips_hd9945_korb_und_originalteil_beleg

Read-only

Das Philips Backset HD9945/01 in den drei erfassten Gerätefamilien gegen den dokumentierten großen Korb abgleichen — Check the actual HD9945 kit and its specified basket.

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>",
      "artikel": "<artikel>",
      "kennung_am_tatsaechlichen_teil": "<kennung_am_tatsaechlichen_teil>"
    },
    "name": "philips_hd9945_korb_und_originalteil_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
korbYesTatsächlich vorgesehener Korb.
geraetYesGenaue Modellfamilie auf dem Gerät.
artikelYesAbgelesene Artikelkennung des angebotenen oder vorhandenen Sets.
kennung_am_tatsaechlichen_teilYesWurde seine Kennung am Artikel selbst oder an der eindeutig zugehörigen Originalpackung verifiziert?

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 the safety and closed-world profile is covered externally. The description adds the useful scope that the comparison spans 'drei erfassten Gerätefamilien' and targets the 'dokumentierten großen Korb', but says nothing about what a match or mismatch looks like, whether any state is recorded, or what happens on ambiguous input — and there is no output schema to fill that gap.

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 naming the resource first, then the action, with no padding. The German and English halves largely restate each other, though the English version adds the 'actual' qualifier, so the duplication costs little but earns little.

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?

All four parameters are required, fully enum'd and documented, and annotations cover the read-only profile, so the definition is callable. However, for a verification tool the description never indicates what outcome the agent should expect (match vs. mismatch vs. ambiguous), and with no output schema this is a real completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with three enums, so the schema carries the baseline. The description still adds interpretive value by contrasting the 'actual' part against the 'documented' basket, which clarifies the intended semantics of the verification flag (kennung_am_tatsaechlichen_teil) and the drei Gerätefamilien reference to the geraet enum. It does not explain how the 'offen' enum options should be handled.

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 pairs a concrete verb ('abgleichen' / 'Check') with a concrete resource (the Philips Backset HD9945/01 kit and its specified basket), so an agent can tell it is a verification tool rather than a listing or lookup tool. It stops short of naming any sibling, so the distinction from overlapping tools such as philips_na35x_max_marke_korb_beobachtung or philips_hd9945_originalteile_und_fremdteile_pflege must be inferred from the resource wording alone.

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?

There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named or excluded. The comparison framing implies this is a cross-check step, but the agent is left to guess whether it should be called before, after, or instead of the related kit/original-part tools.

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