Skip to main content
Glama

getecoback-raumklima

philips_perfectcare_aufbewahrung_schlauchfach_klett

Read-only

Bei der dokumentierten PerfectCare-7000-Aufbewahrung Schlauchfach und Kabel-Klett aus einem Foto des abgekühlten Exemplars separat nachweisen — Document the distinct hose and cable storage 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": {
      "anleitung_am_geraet_bestaetigt": "<anleitung_am_geraet_bestaetigt>",
      "gleiches_exemplar": "<gleiches_exemplar>",
      "schlauchfach": "<schlauchfach>",
      "kabel_klett": "<kabel_klett>"
    },
    "name": "philips_perfectcare_aufbewahrung_schlauchfach_klett"
  }
}

Input Schema

NameRequiredDescriptionDefault
kabel_klettYesIst der Klettverschluss für das Kabel im eigenen Protokoll eindeutig erfasst?
schlauchfachYesIst die Zuordnung des Schlauchs zum Fach im eigenen Protokoll eindeutig?
gleiches_exemplarYesSind beide Fotos oder Beobachtungen demselben abgekühlten Gerät zugeordnet?
anleitung_am_geraet_bestaetigtYesIst genau die verlinkte west-europäische Anleitungsrevision dem eigenen Gerät zugeordnet?

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 the safety profile is covered. The description adds a genuine behavioral constraint beyond that: the two storage features must be evidenced separately and traced to a photo of the cooled exemplar. It still says nothing about what happens with 'offen' or 'abweichend' outcomes or whether anything is persisted.

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?

The single sentence is front-loaded with the condition and the subject, but it is given twice (German then a near-verbatim English restatement) without adding information. The duplicated phrasing costs space that could have carried usage or outcome detail.

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?

Four required parameters are fully documented in the schema and there is no output schema, so the main open question is procedural: what constitutes acceptable evidence and what the tool returns or changes. The description covers the evidence-source prerequisite but leaves those gaps, which is adequate but not complete for a verification-style tool.

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 every parameter, including both enums, is documented in the schema itself. The description adds only that hose and cable evidence are distinct, which is a mild framing cue rather than new meaning for any single parameter, so the baseline 3 applies.

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 (Schlauchfach and Kabel-Klett on the PerfectCare-7000 storage setup) and the evidence context (a photo of the cooled unit), but the operative verb 'nachweisen' / 'Document' is ambiguous about whether this records a claim, validates one, or stores an observation. It does not clearly differentiate itself from nearby evidence-recording siblings such as trageverriegelung_exemplarbeleg or wassertank_entnahme_eigenes_exemplar.

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 an implied precondition (the unit must have cooled, and evidence comes from a photo), but no explicit when-to-use, when-not-to-use, or named alternative. An agent gets no routing signal for choosing this over the other Philips PerfectCare evidence 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