Skip to main content
Glama

getecoback-raumklima

spueler_haertebereich_versorger_geraetestufe

Read-only

Wasserhärte vom Versorger auf Zulaufbezug und nutzbaren Zahlenwert prüfen — Check if household inlet evidence is suitable for a device-specific hardness table.

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": {
      "angabe": "<angabe>",
      "versorgungsbezug": "<versorgungsbezug>"
    },
    "name": "spueler_haertebereich_versorger_geraetestufe"
  }
}

Input Schema

NameRequiredDescriptionDefault
angabeYesWelche Angabe liegt vor?
versorgungsbezugYesWelche Stelle deckt die Angabe ab?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 without description help. The description adds that this is a suitability/classification check rather than a data lookup, but it does not disclose what the verdict looks like or how the four angabe/versorgungsbezug combinations are judged, and there is no output schema to fill that 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?

Two compact clauses, German plus an English gloss, with the core check stated first. No filler sentences, though the bilingual duplication slightly inflates length without adding 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?

For a two-enum, read-only classification tool with full schema coverage and no output schema, the description covers purpose, inputs and the decision context adequately. The one missing piece is what the result of the check looks like, which matters a little given the absence of an output schema.

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% and both parameters are enums with their own descriptions, so the schema carries the parameter burden. The description loosely maps its two criteria to the two inputs ('Zulaufbezug' to versorgungsbezug, 'nutzbaren Zahlenwert' to angabe) but adds no enum meanings or decision rules beyond that.

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 uses a specific verb ('prüfen' / 'Check') on a specific resource ('Wasserhärte vom Versorger') with two named dimensions: inlet reference ('Zulaufbezug') and usable numeric value ('nutzbaren Zahlenwert'). It is clearly distinct from installation-fit siblings, though it never names an alternative tool 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 implied by the condition checked ('suitable for a device-specific hardness table'), so an agent can infer that this applies when a utility hardness statement must be validated before being used. There is no explicit when-not guidance and no mention of sibling tools that handle related hardness or salt questions.

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