Skip to main content
Glama

getecoback-raumklima

philips_wasserhaerte_teststreifen_rote_quadrate_aromamenue

Read-only

Ordnet die dokumentierten roten Quadrate eines Philips-Wasserhärtetests dem Einstellwert am Aromastärke-Symbol zu — Validate a water-hardness setting separately from beverage aroma strength.

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": {
      "modell": "<modell>",
      "streifen_dem_standort_zugeordnet": "<streifen_dem_standort_zugeordnet>",
      "rote_quadrate": "<rote_quadrate>",
      "menue": "<menue>"
    },
    "name": "philips_wasserhaerte_teststreifen_rote_quadrate_aromamenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
menueYesBeobachteter Bezug des Aromastärke-Symbols.
modellYesVollständige Philips-2200-Kennung.
rote_quadrateYesAnzahl sicher roter Teststreifenfelder.
streifen_dem_standort_zugeordnetYesOriginalergebnis ist für das verwendete Wasser und dieses Modell samt Herstelleranleitung belegt.

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 safety and scope are covered. The description adds that the operation works on 'documented' observations and is a validation step, but says nothing about what it returns, whether it rejects inconsistent combinations, or how 'offen' (open/undetermined) inputs are 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?

A single front-loaded sentence with no filler, and the German/English pairing aids comprehension. The English half is largely a restatement of the German half, which is mild redundancy but keeps it short overall.

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?

All four required parameters are documented in the schema, and the tool is a simple read-only mapping with no output schema to explain. Still, the description does not state what the validation result looks like or how ambiguous inputs (enum 'offen') affect the outcome, which an agent would want before calling.

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% with enums on modell and menue, so the schema carries the parameter burden and the baseline of 3 applies. The description only echoes the red-squares input and the aroma-strength menu context, adding no format or semantics beyond the structured fields.

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 names a concrete operation (mapping documented red test-strip squares to the setting at the aroma-strength symbol) and explicitly scopes it apart from beverage aroma strength. The German sentence plus English gloss make the intent readable, though the tool name alone is opaque and no sibling is named as the alternative.

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 clause 'separately from beverage aroma strength' implies a boundary condition for when this tool applies rather than a related one, which is useful implied guidance. However, there is no explicit when-to-use/when-not-to-use statement and no named alternative tool for the aroma-strength case, leaving routing 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