Skip to main content
Glama

getecoback-raumklima

balkon_schirmstellung_freie_spur_vergleich

Read-only

Vergleicht frei gemessene Durchgangsbreiten in zwei bereits genutzten Schirmstellungen — Compare the observed walkway beside a movable sunshade in two existing positions.

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": {
      "spur_a_mm": "<spur_a_mm>",
      "spur_b_mm": "<spur_b_mm>",
      "persoenlicher_bedarf_mm": "<persoenlicher_bedarf_mm>",
      "zusatzspiel_mm": "<zusatzspiel_mm>"
    },
    "name": "balkon_schirmstellung_freie_spur_vergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
spur_a_mmYesEngste beobachtete freie Spur in der ersten Schirmstellung in mm.
spur_b_mmYesEngste beobachtete freie Spur in der zweiten Schirmstellung in mm.
zusatzspiel_mmYesSelbst gewünschter zusätzlicher Platz in mm.
persoenlicher_bedarf_mmYesSelbst gemessener Breitenbedarf des üblichen Wegs in mm.

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 the safety profile is covered. However, the description never discloses the actual comparison logic — whether each observed spur is checked against personal need plus extra clearance, or what verdict is produced. For a purely computational tool with no output schema, that behavioral core is left unexplained.

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?

The single sentence is front-loaded with the verb and resource, which is good. But the German and English halves are near-verbatim duplicates, effectively doubling length without adding any 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?

All four required parameters are covered and the read-only nature is signaled by annotations, so the basics are in place. What is missing is the result semantics — an agent cannot tell from the description whether the output is a boolean adequacy check, a per-position margin, or a recommendation.

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 all four parameters are already documented in the schema, making 3 the baseline. The description reinforces the 'observed' nature of the two spur measurements but adds nothing about how 'zusatzspiel_mm' and 'persoenlicher_bedarf_mm' enter the comparison.

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 gives a specific verb and resource: comparing observed free walkway widths ('frei gemessene Durchgangsbreiten') across two existing sunshade positions. It is clearly a comparison tool rather than a measurement or estimation tool, though it never names a sibling to contrast with.

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?

The phrase 'in zwei bereits genutzten Schirmstellungen' implies a usage constraint: only already-occupied positions can be compared, not hypothetical ones. Beyond that implicit boundary there is no when-to-use/when-not guidance and no routing to alternatives such as the shading-edge or free-section siblings.

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