Skip to main content
Glama

getecoback-raumklima

maehroboter_service_passage_ereignisstelle

Read-only

Wiederkehrende Haltepunkte in einer bestehenden Passage auf eine Beobachtungszone eingrenzen — Locate a repeated observed stop for model-specific yard support.

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": {
      "passage_cm": "<passage_cm>",
      "erster_punkt_cm": "<erster_punkt_cm>",
      "weiterer_punkt_cm": "<weiterer_punkt_cm>",
      "selbe_fahrtrichtung": "<selbe_fahrtrichtung>"
    },
    "name": "maehroboter_service_passage_ereignisstelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
passage_cmYesBereits bekannter Weg von Beginn bis Ende der untersuchten Passage in cm.
erster_punkt_cmYesErster beobachteter Haltepunkt gemessen ab Beginn in cm.
weiterer_punkt_cmYesWeiterer beobachteter Haltepunkt ab demselben Beginn in cm.
selbe_fahrtrichtungYesGab es beide Ereignisse aus derselben Richtung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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. The description adds little beyond the basic purpose: it does not explain what result is produced, how the observation zone is determined, or what role 'selbe_fahrtrichtung' plays in the behavior.

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 definition is short and front-loaded, but the bilingual presentation and the vague phrase 'model-specific yard support' weaken clarity. It is appropriately sized, though not every phrase earns its place.

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?

For a four-parameter calculation or validation tool with no output schema, the description should explain what is returned and how the two observed points and direction flag relate. Instead it leaves the output and decision logic unspecified.

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 parameter is already well documented in the schema. The description mentions passage and stop points in general terms but does not add format, relationship, or validation meaning beyond the schema.

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 resource (repeated stop points in an existing passage) and an action (narrowing to an observation zone), but the phrasing is ambiguous and the English sentence introduces an unrelated-sounding 'model-specific yard support' purpose. It does not clearly distinguish this tool from sibling passage tools such as maehroboter_passage_seitenspiel.

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?

It gives no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The only contextual cue is 'bestehende Passage', which is implied rather than stated as a usage rule.

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