Skip to main content
Glama

getecoback-climate-weather

duschgriff_zwei_nutzende_gemeinsame_ablage

Read-only

Eine tatsächlich erreichbare Brausenablage für zwei nacheinander nutzende Personen finden — Find a shared reachable position from two independent observations.

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_person_1": "<a_person_1>",
      "a_person_2": "<a_person_2>",
      "b_person_1": "<b_person_1>",
      "b_person_2": "<b_person_2>",
      "beobachtungen_komplett": "<beobachtungen_komplett>"
    },
    "name": "duschgriff_zwei_nutzende_gemeinsame_ablage"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_person_1YesPerson 1 erreicht den Griff an A in ihrer vorgesehenen Nutzungslage.
a_person_2YesPerson 2 erreicht den Griff an A in ihrer vorgesehenen Nutzungslage.
b_person_1YesPerson 1 erreicht den Griff an B.
b_person_2YesPerson 2 erreicht den Griff an B.
beobachtungen_komplettYesBeide Personen haben beide vorgesehenen Ablagepositionen tatsächlich erprobt.

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 agent knows this is a side-effect-free, closed-world computation. The description adds the framing of combining two independent observations, but says nothing about what the 'beobachtungen_komplett' gate does when false, nor what a negative result means. No contradiction with annotations.

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 sentence with the goal front-loaded, plus a bilingual restatement. The German/English duplication is mildly redundant but costs little and aids disambiguation of an unusual domain metaphor, so the wording largely earns its place.

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?

With five required booleans, full schema coverage, and no output schema, the description should carry the return-value burden — but it never states what 'finding' produces or how the completeness flag alters the outcome. Adequate to invoke, but incomplete for interpreting the result.

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 one of the five booleans is already documented in German within the schema. The description only implies the A/B pairing via 'two independent observations' and adds no format, ordering, or edge-case semantics beyond that, so the baseline 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 concrete goal — find a shared reachable position for two people from two independent observations — which is more specific than a tautology of the tool name. However, the shower-shelf framing ('Brausenablage') obscures the actual computational semantics: whether the tool returns position A, position B, neither, or a boolean feasibility verdict. It also gives no cue to distinguish it from close siblings such as duschgriff_blickverdeckung_und_tatsaechliche_erreichbarkeit.

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?

There is no statement of when to use this tool, when not to, or which sibling covers the adjacent case. The phrase 'two nacheinander nutzende Personen' hints at the scenario (sequential use), but prerequisites and exclusions are absent, leaving the agent to infer selection from the name alone.

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