Skip to main content
Glama

getecoback-climate-weather

philips_azur_sohle_pflegeaussage_eigener_nachweis

Read-only

Beim DST7040 einen angebotenen Sohlenreiniger von den ausdrücklich ausgeschlossenen Reinigungsarten unterscheiden — Classify a proposed soleplate cleaning method against the Azur manual.

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": {
      "dst7040_belegt": "<dst7040_belegt>",
      "pflegeart": "<pflegeart>"
    },
    "name": "philips_azur_sohle_pflegeaussage_eigener_nachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
pflegeartYesGeprüfte Reinigungsart für die Bügelsohle.
dst7040_belegtYesIst die Geräteanleitung für das eigene DST7040 bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds that the classification is against the Azur manual and concerns explicitly excluded cleaning methods, but it does not explain what result the agent should expect or how the dst7040_belegt gate affects the answer.

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?

The description is compact and front-loads the core classification task. The bilingual phrasing is slightly redundant but does not obscure the meaning.

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 simple two-parameter, read-only classification tool, the description covers the main purpose and manual basis. However, with no output schema, it should say more about what the classification returns, especially when dst7040_belegt is false or pflegeart is 'unbekannt'.

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%, so both parameters and the pflegeart enum are already documented. The description only adds general context that pflegeart is a proposed soleplate cleaning method to be checked against excluded types; it does not clarify how individual enum values should be interpreted.

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 states a specific action: classify a proposed soleplate cleaning method against the Azur manual for the DST7040. It is clear what the tool does, though it does not explicitly distinguish itself from any named sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used when checking whether a proposed soleplate cleaner is one of the excluded cleaning types. It does not state when not to use the tool or point to any alternative.

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