Skip to main content
Glama

getecoback-raumklima

haushaltsweg_begegnung_freie_breite

Read-only

Prüfen, ob zwei gemessene getragene Gegenstände einander in einem geplanten gemeinsamen Durchgangsabschnitt begegnen könnten — Check simultaneous passage width for two carried household items.

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": {
      "engstelle_cm": "<engstelle_cm>",
      "a_gesamt_cm": "<a_gesamt_cm>",
      "b_gesamt_cm": "<b_gesamt_cm>",
      "trennreserve_cm": "<trennreserve_cm>"
    },
    "name": "haushaltsweg_begegnung_freie_breite"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_gesamt_cmYesGemessene gesamte Breite von Person und Gegenstand A in Transportausrichtung.
b_gesamt_cmYesGemessene gesamte Breite von Person und Gegenstand B in Transportausrichtung.
engstelle_cmYesTatsächlich kleinste freie Breite im betreffenden geraden Abschnitt.
trennreserve_cmYesEigener zusätzlich geplanter Zwischenraum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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, and the description is consistent with them (a pure check, no mutation). Beyond that, the description adds nothing behavioral: it does not say whether the check returns a boolean, a remaining clearance, or a margin, whether the Trennreserve is added or subtracted, or whether the comparison is strict — and with no output schema those gaps stay unfilled.

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 content is front-loaded and short, but the German sentence is immediately repeated in English, which is pure duplication rather than added information. Removing one language would lose nothing an agent needs.

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?

This is a four-required-parameter computation tool with no output schema, so the description is the only place the result contract could be stated — and it is silent on what comes back and how the values are combined. For a decision/compute tool, that leaves a material gap despite the fully documented input schema.

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 (engstelle_cm, a_gesamt_cm, b_gesamt_cm, trennreserve_cm) are already documented in the schema. The description only gestures at the same concepts ('getragene Gegenstände', 'freie Breite') without adding formula, units nuance, or tolerance semantics, so the baseline applies.

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 (Prüfen/check) and a specific resource (simultaneous passage width for two carried household items meeting in a shared corridor section), so an agent can tell exactly what the call computes. It does not, however, contrast itself with any sibling tool, so the differentiation leg of the rubric is unmet.

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?

The description states what is checked but never says when to reach for this tool versus any alternative, nor any precondition or exclusion. The phrase 'in einem geplanten gemeinsamen Durchgangsabschnitt' hints at a planning context, but that is an implied setting rather than explicit usage guidance.

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