Skip to main content
Glama

getecoback-climate-weather

philips_perfectcare_zweistundenangabe_eigene_arbeitszeit

Read-only

Den oberen Zwei-Stunden-Werbewert der PSG7140/70 mit der Nettozeit eines eigenen protokollierten Durchgangs beschreiben — Isolate observed active time from the maker’s up-to-two-hours statement.

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>",
      "durchlauf_belegt": "<durchlauf_belegt>",
      "brutto_min": "<brutto_min>",
      "pausen_min": "<pausen_min>",
      "nachfuellungen": "<nachfuellungen>"
    },
    "name": "philips_perfectcare_zweistundenangabe_eigene_arbeitszeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
brutto_minYesVerstrichene beobachtete Minuten.
pausen_minYesDarin enthaltene, separat beobachtete Pausen in Minuten.
nachfuellungenYesSeparat beobachtete Anzahl weiterer Tankfüllungen, ohne die Startfüllung.
durchlauf_belegtYesStart, Ende und Pausen aus demselben beobachteten Durchlauf?
psg7140_70_belegtYesIst genau die eigene /70 Variante bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 idea — separating observed active time from the manufacturer's marketing statement — but with no output schema it does not say what the result looks like, nor how it handles the confirmed/unconfirmed boolean flags.

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?

It is a single front-loaded sentence with no padding. The only waste is the near-duplicate English restatement of the German clause, which repeats the same idea rather than extending it.

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 five-required-parameter derivation tool with no output schema, the definition should indicate what is returned and how the boolean confirmations gate the computation. Those gaps remain, though the schema itself carries most of the needed input context.

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 all five parameters are already documented with ranges and German explanations (elapsed minutes, contained pauses, extra refills, run-confirmation and exact-variant flags). The description adds no further parameter meaning and does not explain that net time is derived from brutto_min minus pausen_min.

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 a specific resource (the PSG7140/70's stated upper two-hour rating) and a specific operation (relate it to the net time of one's own logged run, isolating observed active time from the maker's claim). The verb 'beschreiben' is vague, however, and it never states the concrete operation performed (presumably net time = elapsed minus pauses, compared against the claim), so an agent must guess the actual computation.

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 guidance and no mention of any alternative among the many sibling Philips observation/comparison tools. The scenario is only implied by the phrasing 'eigene protokollierter Durchgang' vs. 'Werbewert', leaving the agent to infer when this tool is the right choice over, for example, the refill-timing or motion-sensor observation siblings.

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