Skip to main content
Glama

getecoback-climate-weather

philips_azur_wasserzusatz_anleitung_abgrenzung

Read-only

Eine einzelne Flüssigkeit im Azur DST7040 der dokumentierten Liste ausgeschlossener Zusätze und Wässer zuordnen — Check a single liquid or additive 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>",
      "fluessigkeit": "<fluessigkeit>"
    },
    "name": "philips_azur_wasserzusatz_anleitung_abgrenzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
fluessigkeitYesBekannte Herkunft der gewählten Flüssigkeit.
dst7040_belegtYesOrdnet die Kennzeichnung das Gerät der gelesenen DST7040 Anleitung zu?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the check is against a documented exclusion list in the manual, which is useful closed-world context, but it says nothing about what the result contains or how an inconclusive/'unbekannt' liquid is handled.

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?

One compact sentence front-loaded with the action and scope, followed by an English restatement. The bilingual duplication is slightly redundant but aids comprehension 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.

Completeness3/5

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

With no output schema, the description carries the burden of explaining what a classification result looks like, and it does not — an agent cannot tell whether the tool returns a boolean, a category, or a citation to the manual. For a low-complexity two-parameter read tool the rest is adequate.

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% with only two parameters, so the schema already documents both. The description adds marginal value by framing the operation as mapping a liquid to the manual's list and by tying the DST7040 identification to 'dokumentierte' assignment, consistent with the dst7040_belegt parameter, but adds no format or edge-case detail.

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 gives a specific verb ('zuordnen' / classify) and a specific resource ('eine einzelne Flüssigkeit' against the documented list of excluded additives and waters for the Azur DST7040). The word 'einzelne' signals single-item scope, which implicitly separates it from batch/mixing siblings, though no sibling is named explicitly.

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?

Usage is only implied: the agent can infer this is for checking one liquid at a time against the manual's exclusion list. There is no explicit statement of when to prefer this over an alternative tool, and no exclusions or prerequisites are given.

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