Skip to main content
Glama

getecoback-raumklima

maehroboter_passage_seitenspiel

Read-only

Freiraum zwischen starren Hindernissen in einer vorhandenen Mähroboterpassage dokumentieren — Compare usable passage width with a location-specific manual requirement for an installed mower.

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": {
      "lichte_cm": "<lichte_cm>",
      "einragend_cm": "<einragend_cm>",
      "anleitung_cm": "<anleitung_cm>",
      "genaue_fuehrung": "<genaue_fuehrung>"
    },
    "name": "maehroboter_passage_seitenspiel"
  }
}

Input Schema

NameRequiredDescriptionDefault
lichte_cmYesLichte Breite an der engsten Stelle zwischen festen Hindernissen.
anleitung_cmYesPassagenbreite für genau dieses Modell und Führungssystem in Zentimetern.
einragend_cmYesZusätzlich gemessene Einragung von Ästen oder Kanten innerhalb dieser Breite.
genaue_fuehrungYesBreitenangabe gilt ausdrücklich für diese Führung und für diese Passagenart?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety profile is covered; the description is consistent with a pure read/compute operation ('dokumentieren', 'Compare'). It adds the idea that the comparison is against a location-specific manual figure, but says nothing about what the comparison yields (verdict, margin, tolerance) or how protrusions are folded in.

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-loads the German statement, but the English clause largely restates the same content rather than extending it, so roughly half the text is duplicative. The purpose is still recoverable quickly, hence a middling score rather than a poor one.

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 four required parameters, no output schema, and a computation-style tool, the description should clarify what is returned (e.g., a pass/fail against the manual width or the remaining margin). It covers the input side adequately but leaves the result shape unstated, so it is only partially complete for this 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%, so each of the four parameters is already explained in the schema, which sets the baseline at 3. The description reinforces the pairing of measured width (lichte_cm) with the required width (anleitung_cm), but adds no units, tolerance rules, or handling of einragend_cm beyond what the schema states.

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 concrete action and object: documenting the free space between rigid obstacles in an existing mower passage and comparing usable width against a location-specific manual requirement. That is a specific verb+resource, and the notion of comparing measured vs. required width is distinct from the garden-check/maehfenster siblings. It does not explicitly say how it differs from the sibling tools, which keeps it at 4 rather than 5.

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 explicit when-to-use or when-not-to-use statement and no alternative named. The phrase 'in einer vorhandenen Mähroboterpassage' hints that the passage must already exist, but the agent is left to infer that this tool applies only when a manual spec is available for the exact model and guide system.

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