Skip to main content
Glama

getecoback-climate-weather

miele_g7673_schwankende_wasserhaerte_oberwert

Read-only

Bei dokumentiert schwankender Härte am Miele-Zulauf den vorgesehenen Höchstwert ausweisen — Read what the exact Miele manual calls for with a verified inlet range.

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": {
      "anleitung_bestaetigt": "<anleitung_bestaetigt>",
      "intervall_grund": "<intervall_grund>",
      "unterwert_dh": "<unterwert_dh>",
      "oberwert_dh": "<oberwert_dh>"
    },
    "name": "miele_g7673_schwankende_wasserhaerte_oberwert"
  }
}

Input Schema

NameRequiredDescriptionDefault
oberwert_dhYesBelegter Zahlenwert der Wasserhärte am Zulauf in °dH.
unterwert_dhYesBelegter Zahlenwert der Wasserhärte am Zulauf in °dH.
intervall_grundYesWarum liegen zwei Werte vor?
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 result is anchored in the exact Miele manual with a verified inlet range, which is useful behavioral context, but it does not state how the fluctuating interval is resolved (presumably the higher value is reported) or what is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and the German clause is front-loaded, but the English half largely restates the German ('verified inlet range' versus 'dokumentiert schwankender Härte') rather than adding new information. The bilingual duplication spends words without earning them.

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 four-required-parameter, read-only derivation tool with no output schema, the definition should make clear what the returned maximum is and how it is derived. It gestures at this ('den vorgesehenen Höchstwert ausweisen') but leaves the derivation rule and return value implicit, which is a meaningful gap.

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%, so every parameter is already documented in the schema, including the enum for 'intervall_grund' and the meaning of 'anleitung_bestaetigt'. The description adds no additional meaning about units, value ranges, or how the lower/upper pair should be supplied, so the baseline of 3 applies.

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 operation on a specific subject: report the designated maximum value (°dH) when inlet hardness fluctuates at the Miele appliance. However, the verb is ambiguous — it blends 'declare a value' with 'read what the manual calls for' — and it never explains the relationship to the required 'unterwert_dh' parameter, so an agent cannot fully tell what the tool produces versus what it looks up.

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 trigger condition is implied by 'Bei dokumentiert schwankender Härte am Miele-Zulauf', which is more than nothing. But there are no explicit exclusions or routing to alternatives such as the water-hardness interval or test-strip siblings, so the agent must infer when this tool is the right choice over them.

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