Skip to main content
Glama

getecoback-climate-weather

philips_perfectcare_schlauchpfad_reichweite_reserve

Read-only

Bei der PSG7140/70 einen gemessenen Schlauchweg inklusive eigener Bewegungsreserve mit der dokumentierten Gesamtlänge abgleichen — Compare the workspace path and user reserve with the listed hose length.

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>",
      "weg_belegt": "<weg_belegt>",
      "gemessener_weg_cm": "<gemessener_weg_cm>",
      "eigene_bewegungsreserve_cm": "<eigene_bewegungsreserve_cm>"
    },
    "name": "philips_perfectcare_schlauchpfad_reichweite_reserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
weg_belegtYesIst der tatsächliche freie Weg getrennt von der geraden Entfernung gemessen?
gemessener_weg_cmYesTatsächlich erforderliche Weglänge in cm, bereits mit bestätigten Umwegen.
psg7140_70_belegtYesIst PSG7140/70 exakt belegt?
eigene_bewegungsreserve_cmYesZusätzliche eigene Organisationsreserve in cm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish this is a read-only, closed-world operation, so the safety profile is covered. Beyond that the description says nothing about how the comparison resolves — whether it reports a difference, a pass/fail verdict, or a tolerance threshold — which is the only behavior that matters for a comparison tool.

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 a single front-loaded sentence, but roughly half of it is an English mirror of the German clause rather than new information, and the two clauses drift in wording ('Schlauchweg/Bewegungsreserve' vs. 'workspace path/user reserve'). The duplication costs tokens without adding meaning for a term this domain-specific.

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?

All four required parameters are fully documented and the tool is a simple deterministic check, but there is no output schema and the description never states what the comparison yields. For a tool whose entire value is the comparison result, the agent is left guessing how to interpret or relay the response.

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 coverage is 100% and every parameter carries a German description with units and bounds, so the schema does the heavy lifting. The description restates the conceptual pairing (measured path + own reserve vs. total length) but adds no format, unit, or edge-case detail beyond the schema; baseline 3 applies.

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 concrete verb (abgleichen/compare) and concrete objects (measured hose path plus own movement reserve vs. documented total length) scoped to the PSG7140/70. An agent understands the operation without opening the schema, though nothing in the text distinguishes it from the many other Philips PerfectCare tools that also deal with documented values.

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 when-to-use statement, no prerequisite (e.g. that the documented total length must already be known), and no alternative tool is mentioned for cases where the path has not been measured. The only implicit context is the 'Bei der PSG7140/70' clause and the required psg7140_70_belegt flag.

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