Skip to main content
Glama

getecoback-climate-weather

duschgriff_blickverdeckung_und_tatsaechliche_erreichbarkeit

Read-only

Einen verdeckten Griff von einem tatsächlich nicht erreichten Griff unterscheiden — Keep view obstruction separate from an observed reach limitation.

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": {
      "blick_beobachtet": "<blick_beobachtet>",
      "sicht_frei": "<sicht_frei>",
      "greifprobe_beobachtet": "<greifprobe_beobachtet>",
      "griff_erreicht": "<griff_erreicht>",
      "lage_gleich": "<lage_gleich>"
    },
    "name": "duschgriff_blickverdeckung_und_tatsaechliche_erreichbarkeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
sicht_freiYesGriff war in dieser Nutzungslage sichtbar.
lage_gleichYesSicht- und Greifbeobachtung stammen aus derselben bezeichneten Position.
griff_erreichtYesDer Griff wurde persönlich erreicht.
blick_beobachtetYesSicht auf den vorgesehenen Griff in der eigenen Nutzungslage tatsächlich beobachtet.
greifprobe_beobachtetYesDie persönliche Reichweite wurde unabhängig beobachtet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the bar is lower. Beyond that the description adds only conceptual framing: it says nothing about how the five booleans are combined, what the distinction is expressed as, what happens when lage_gleich is false, or whether conflicting inputs are rejected. For a five-required-boolean decision tool this leaves real behavioral gaps.

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 short sentences with the core distinction front-loaded in the first clause. The English second sentence is essentially a translation of the German and therefore redundant, but the overall length is tight and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five required booleans and no output schema, the description should say what the tool returns or how the resulting distinction is conveyed, and it does not. Combined with missing guidance on invalid combinations (e.g. observations from different positions) and on the read-only nature of the check, it is under-specified for the tool's complexity.

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 boolean carries a clear German gloss, so the schema does the parameter work. The description's wording ('verdeckt' vs 'tatsächlich nicht erreicht') frames the semantics of sicht_frei and griff_erreicht but adds no interpretation, defaults, or edge-case meaning beyond the schema text.

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 states a specific discriminating task: telling an obstructed-view grip apart from a grip that was genuinely not reached, and the English addendum makes the distinction explicit. An agent can grasp the intent, though the tool's operation is framed as a conceptual separation rather than a concrete action with a stated result, and no sibling is named for contrast.

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 only implied: the agent should reach for this when a view observation and a reach observation both exist and might be conflated. There is no explicit when-to-use condition tied to the sibling tools, no statement of prerequisites (e.g. that both observations come from the same position), and no exclusion telling the agent when this distinction is unnecessary.

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