Skip to main content
Glama

getecoback-climate-weather

maehroboter_gatter_durchfahrt_richtung_paare

Read-only

Bei einer beobachteten Tordurchfahrt fehlenden Rückweg getrennt festhalten — Check directional passage evidence for each leg of a supervised trip.

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": {
      "hin_pruefungen": "<hin_pruefungen>",
      "hin_komplett": "<hin_komplett>",
      "rueck_pruefungen": "<rueck_pruefungen>",
      "rueck_komplett": "<rueck_komplett>",
      "gleiches_tor_und_system": "<gleiches_tor_und_system>"
    },
    "name": "maehroboter_gatter_durchfahrt_richtung_paare"
  }
}

Input Schema

NameRequiredDescriptionDefault
hin_komplettYesDavon vollständig befahren.
hin_pruefungenYesVollständig beobachtete Hinversuche.
rueck_komplettYesDavon vollständig befahren.
rueck_pruefungenYesVollständig beobachtete Rückversuche.
gleiches_tor_und_systemYesGleiches System, gleicher Torzustand und laut Anleitung vorgesehener Weg?

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 essentially nothing beyond that: it does not say how the counts are combined, whether 'komplett' values must be ≤ the corresponding 'pruefungen' values, whether mismatches are rejected or reported, or what the caller receives back. For a validation-style tool this is a meaningful gap.

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, which is good, but the two-language phrasing is not a translation of the same claim and creates ambiguity rather than redundancy. The em-dash construction reads like a note rather than a tool specification, and the space is spent on restatement rather than the real semantics.

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?

A read-only tool taking five required numeric/boolean inputs with no output schema needs the description to explain what the result represents (a boolean check? per-leg ratios? a gap report?). None of that is present, and the ambiguous German clause about 'festhalten' actively muddies whether the tool merely evaluates or records something. Inadequate 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 coverage is 100% and all five parameters are required with their own descriptions, so the schema does the heavy lifting. The description only marginally adds to that, indicating that outbound ('Hin') and return ('Rück') legs are handled separately — which is already visible from the parameter names hin_pruefungen/rueck_pruefungen. Baseline 3 applies.

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 verb ('Check ... evidence') and an object ('directional passage evidence for each leg of a supervised trip'), so the general intent is graspable. But the German half ('fehlenden Rückweg getrennt festhalten') says something different in emphasis — record a missing return leg separately — and neither half explains what the tool actually computes from the five counts. It also gives no differentiation from near-identical siblings such as maehroboter_passage_seitenspiel or maehroboter_service_passage_ereignisstelle.

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 a hint of context ('bei einer beobachteten Tordurchfahrt', 'supervised trip') but no explicit statement of when to call this versus the other maehroboter observation tools. No prerequisites, no exclusions, and no criteria for choosing among the many passage-related siblings are given.

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