Skip to main content
Glama

getecoback-raumklima

philips_perfectcare_energiesparangabe_normal_max_bezug

Read-only

Den beworbenen Energievergleich der PSG7140/70 auf genau die dokumentierten Gerätemodi und den genannten Prüfbezug begrenzen — Match the maker’s energy comparison to the stated modes and test basis.

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>",
      "gegenstand": "<gegenstand>",
      "pruefnorm_belegt": "<pruefnorm_belegt>"
    },
    "name": "philips_perfectcare_energiesparangabe_normal_max_bezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
gegenstandYesWorauf sich die zu bewertende Aussage bezieht.
pruefnorm_belegtYesIst derselbe Hersteller-Prüfbezug IEC 60331-1 in der Aussage ausdrücklich angegeben?
psg7140_70_belegtYesIst genau PSG7140/70 für diese Angabe bestätigt?

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 declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds no behavioral context beyond the constraint concept: it does not say what is returned, how a non-matching claim is reported, or what happens when the enum is 'unbekannt'. For a read-only assessment tool that would need little disclosure, this is a notable gap.

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?

Very short and front-loaded, with the constraining action stated first. The bilingual German/English duplication is mildly redundant but inexpensive and does not bury the key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and only three fully documented parameters, the description supplies enough to call the tool correctly, and its stated constraint aligns with the parameters. The missing piece is what the result looks like, which is a moderate rather than severe gap for a read-only check.

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%, including an enum and two booleans with individual descriptions, so the schema carries parameter meaning on its own. The description's mention of 'documented modes' and 'test basis' loosely maps to gegenstand and pruefnorm_belegt but adds no syntax or interpretation beyond the schema.

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 claim (the advertised energy comparison of the PSG7140/70) and a specific action (restrict it to documented device modes and the stated test basis), which is more than a restatement of the opaque name. However, it never states what the tool operationally produces — a verdict, a scoping statement, or a corrected wording — so an agent cannot fully predict its output from the purpose alone.

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 or when-not-to-use guidance and no named alternative among the many sibling scope-check tools. The intended trigger (evaluating a manufacturer energy-saving claim about the PSG7140/70) is only implied by the phrasing 'beworbenen Energievergleich'.

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