Skip to main content
Glama

getecoback-climate-weather

brauseschlauch_anschluesse_abgleichen

Read-only

Beide Enden eines Ersatz-Brauseschlauchs mit Armatur und Handbrause abgleichen — Check both ends of a replacement shower hose against the documented connectors.

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": {
      "armatur": "<armatur>",
      "brause": "<brause>",
      "schlauch_armatur": "<schlauch_armatur>",
      "schlauch_brause": "<schlauch_brause>"
    },
    "name": "brauseschlauch_anschluesse_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
brauseYesDokumentierte Größe an der Handbrause.
armaturYesDokumentierte Größe an der Armatur.
schlauch_brauseYesDokumentierte Größe am Brauseende des Schlauchs.
schlauch_armaturYesDokumentierte Größe am Armaturende des Schlauchs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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, and the description is consistent with a pure comparison against documented values. It adds the useful scope note that both hose ends are checked against their respective counterparts, but says nothing about what the comparison produces (match/mismatch, which side fails) or how 'unbekannt' is treated.

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

Conciseness3/5

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

A single sentence is front-loaded with the core action, which is good. However, the German sentence and its English translation restate the same content verbatim, roughly doubling length without adding 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?

For a read-only four-parameter comparison with fully documented enum parameters, the input side is adequately covered. With no output schema, the description should explain what the comparison returns or how an 'unbekannt' input affects the result; that gap leaves the agent guessing about the response.

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 all four parameters carry enum values with German descriptions, so the schema does the heavy lifting. The description contributes the pairing semantics — armature side and hand-shower side, each with a documented size and a hose-end size — which helps an agent map the four fields correctly, 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 names a specific verb and resource: comparing ("abgleichen") both ends of a replacement shower hose against the documented armature and hand-shower connectors. An agent can tell this is a connector-compatibility check rather than a measurement or estimation tool. It stops short of distinguishing itself from the many other '*_abgleichen' siblings.

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

Usage Guidelines2/5

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

Usage is only implied by the word "Ersatz" (replacement), which suggests the context of swapping a hose. There is no statement of when to call this versus the related shower/flow tools, no prerequisites, and no exclusions such as what to do when a value is unknown.

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