Skip to main content
Glama

getecoback-raumklima

duschhalter_winkel_nutzerwunsch_vorhandene_stellungen

Read-only

Vorhandene Handbrausenstellungen nach belegtem Sprüh- und Bedienwunsch der gleichen Person vergleichen — Compare observed aiming positions without inferring a universal 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": {
      "a_richtung_passt": "<a_richtung_passt>",
      "a_verstellung_erreichbar": "<a_verstellung_erreichbar>",
      "b_richtung_passt": "<b_richtung_passt>",
      "b_verstellung_erreichbar": "<b_verstellung_erreichbar>",
      "beide_geprueft": "<beide_geprueft>"
    },
    "name": "duschhalter_winkel_nutzerwunsch_vorhandene_stellungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
beide_geprueftYesA und B wurden in ähnlicher Nutzungslage und mit der gleichen Brause beobachtet.
a_richtung_passtYesBeobachtete Sprührichtung A deckte den eigenen gewünschten Bereich ab.
b_richtung_passtYesEntsprechender Richtungsbefund in B.
a_verstellung_erreichbarYesErlaubter Griff oder Einstellpunkt war in A persönlich erreichbar.
b_verstellung_erreichbarYesEntsprechender Erreichbarkeitsbefund in B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 structurally. The description adds a real behavioral constraint beyond that — the result must stay person-specific and must not be treated as a universal adjustment range — but it says nothing about what the comparison yields or how conflicting booleans 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.

Conciseness3/5

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

It is short and front-loaded, but the second half is largely an English restatement of the German clause rather than new information, which makes the bilingual pairing slightly redundant. No sentence is wasted outright, though the duplicate phrasing costs some density.

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 comparator over five booleans with full schema coverage and no output schema, the description is roughly adequate — it states the observation basis and the non-generalization rule. It is still incomplete about what the tool returns (a comparison verdict?) and what condition makes the comparison valid, e.g. whether beide_geprueft must be true for other results to matter.

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 each of the five booleans is documented in German, so the baseline is 3. The description maps loosely onto the parameters by naming the two dimensions (Sprühwunsch → a_richtung_passt/b_richtung_passt, Bedienwunsch → the verstellung_erreichbar pair), but adds no format or semantics beyond the schema.

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 does name a verb ("vergleichen") and a resource ("vorhandene Handbrausenstellungen"), plus a scope limit ("ohne universellen Bereich abzuleiten"). But the resource is abstract — 'observed aiming positions' tied to a person's documented spray/operation wish — and no sibling tool is named or contrasted, so an agent cannot easily tell it apart from the other duschhalter_* observation tools.

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?

Implicit usage is present: compare positions only where the observations come from the same person ("der gleichen Person") and do not generalize into a universal range. There is no explicit when-to-use vs. when-not, and no alternative tool is suggested for the case where a general range or a different person is needed.

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