Skip to main content
Glama

getecoback-raumklima

philips_perfectcare_wassertank_entnahme_eigenes_exemplar

Read-only

Bei der PSG7140/70 die Kaufanforderung abnehmbarer Wassertank vom erfassten konkreten Gebrauchtangebot unterscheiden — Verify a detachable tank requirement and specimen evidence.

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>",
      "abnehmbar_erforderlich": "<abnehmbar_erforderlich>",
      "tank_am_exemplar": "<tank_am_exemplar>"
    },
    "name": "philips_perfectcare_wassertank_entnahme_eigenes_exemplar"
  }
}

Input Schema

NameRequiredDescriptionDefault
tank_am_exemplarYesBeleg am angebotenen Exemplar.
psg7140_70_belegtYesIst die vollständige Kennung am angebotenen Gerät belegt?
abnehmbar_erforderlichYesIst separat abnehmbarer Tank eine persönliche Kaufanforderung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety is covered by structured data. The description adds nothing beyond that: it does not say whether the tool returns a verdict, a consistency check, or merely records the classification, nor how the 'offen' case is treated. For a tool with no output schema, that leaves the observable behavior opaque.

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?

Two tightly packed clauses with the device/scope constraint front-loaded and no filler. It is dense but not padded; the bilingual restatement is redundant but brief.

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?

Parameters are fully self-documenting and the read-only nature is clear from annotations, which covers most of what an agent needs. The remaining gap is the return value: with no output schema and no statement of what the tool yields, the agent must guess the result shape.

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 three parameters and the enum are already documented, which sets the baseline at 3. The description does reinforce the central semantic split the parameters encode (personal purchase requirement vs. evidence on the offered specimen), but adds no format, precedence, or default guidance.

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 names a specific device (PSG7140/70), a specific object (abnehmbarer Wassertank) and a specific operation (Kaufanforderung vs. Beleg am konkreten Gebrauchtangebot unterscheiden), so the agent can tell it apart from generic evidence siblings. It stops short of a 5 because it never says what the tool actually produces from that distinction.

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?

Applicability is only implied: the scope is 'bei der PSG7140/70' acting on a 'erfassten konkreten Gebrauchtangebot'. There is no explicit when-not guidance and no named alternative among the many sibling exemplar-evidence tools, so routing must be inferred.

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