Skip to main content
Glama

getecoback-raumklima

philips_perfectcare_ersatzteil_tank_auffangkappe_artikelcode

Read-only

In der deutschen PSG7140/70 Teileliste die Kennungen für Ersatztank und Auffangkappe dem tatsächlichen Angebotscode zuordnen — Verify the listed spare reservoir or collector cap reference.

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": {
      "psg7140_70_belegt": "<psg7140_70_belegt>",
      "rolle": "<rolle>",
      "angebotscode": "<angebotscode>"
    },
    "name": "philips_perfectcare_ersatzteil_tank_auffangkappe_artikelcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
rolleYesTeil, das im eigenen Gerät fehlt.
angebotscodeYesKennung direkt am angebotenen Ersatzteil oder zugeordneter Verpackung.
psg7140_70_belegtYesIst die vollständige Kennung PSG7140/70 des Zielgeräts belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 scope information beyond that — the lookup is confined to the German PSG7140/70 parts list — but says nothing about what a successful or failed verification returns, or how 'andere_oder_offen'/'nicht_belegt' inputs are handled.

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-loaded with the German framing, but the German clause and the English clause largely restate each other ('Ersatztank und Auffangkappe ... Angebotscode zuordnen' vs. 'Verify the listed spare reservoir or collector cap reference'), so the second half adds 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?

For a three-parameter read-only verification tool with no output schema, the definition should at least indicate what the verification yields. The scope and domain are conveyed, but the result semantics an agent needs to interpret the call are missing.

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% and both enum parameters carry their own descriptions, so the schema does the heavy lifting. The description mentions the reservoir/cap subjects that map onto the 'rolle' enum but adds no meaning about how 'psg7140_70_belegt' gates the verification outcome.

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 the resource (spare reservoir / collector cap identifiers in the German PSG7140/70 parts list) and the action (assigning them to an actual offer code, i.e. verifying the reference). However, the bilingual split sentence makes the actual outcome ambiguous — is it a lookup, a validation, or a mapping step? It also gives no cue distinguishing it from the many other ersatzteil_* siblings.

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 statement about when to use this tool versus alternatives, no prerequisites, and no exclusions. Usage is only implied by the domain wording ('in der deutschen PSG7140/70 Teileliste'), leaving the agent to infer the triggering situation.

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