Skip to main content
Glama

getecoback-climate-weather

philips_perfectcare_refill_zeitpunkt_anforderung_beleg

Read-only

Für die PSG7140/70 dokumentiertes Nachfüllen während des Gebrauchs von der behaupteten ununterbrochenen Dampfleistung unterscheiden — Separate the refill capability from a continuous-flow assumption.

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>",
      "anforderung": "<anforderung>",
      "nachfuellvorgang_selbst_erfasst": "<nachfuellvorgang_selbst_erfasst>"
    },
    "name": "philips_perfectcare_refill_zeitpunkt_anforderung_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
anforderungYesEigene zwingende Anforderung.
psg7140_70_belegtYesIst exakt PSG7140/70 am betrachteten Gerät bestätigt?
nachfuellvorgang_selbst_erfasstYesWurde die tatsächliche Unterbrechung am Exemplar bereits selbst dokumentiert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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; the description adds nothing about behavior beyond the conceptual distinction. It never says whether the call validates consistency between the requirement enum and the two booleans, what verdict/format it returns, or what happens when 'psg7140_70_belegt' is false — a real gap given there is no output schema.

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?

Very short, but the second half is essentially an English restatement of the first half rather than new information, and the substantive constraint is not front-loaded ahead of ambiguity about the action. Efficient in length, weak in information density.

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?

A read-only classification tool with three required inputs, an enum, and no output schema should explain what a call produces and how the inputs are combined. The description covers only the motivating distinction, leaving an agent unable to predict the result of invoking it.

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 each of the three required parameters carries its own description plus an enum, so the schema does the work. The description restates the same tension in prose without adding format, allowed combinations, or interpretation rules beyond what the schema provides.

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 domain distinction it operates on (documented refill during use vs. claimed uninterrupted steam output) and the device (PSG7140/70), but never states the action the tool performs — no verb such as 'classify', 'check', or 'assess', and no indication of what a caller gets back. An agent can infer the topic but not the operation.

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 guidance, no prerequisites, and no mention of any alternative — despite many siblings that also concern evidence/Beleg capture. The description only defines the conceptual gap being examined, leaving tool selection to inference.

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