Skip to main content
Glama

getecoback-climate-weather

rollwagen_belagwechsel_richtungsspezifischer_stopp

Read-only

Hält getrennt fest, in welcher Richtung am gleichen beobachteten Bodenwechsel ein zusätzlicher Stopp auftrat — Identify direction-specific pauses at the same already observed flooring transition.

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": "<hin>",
      "rueck": "<rueck>",
      "gleicher_uebergang": "<gleicher_uebergang>"
    },
    "name": "rollwagen_belagwechsel_richtungsspezifischer_stopp"
  }
}

Input Schema

NameRequiredDescriptionDefault
hinYesBefund in Richtung A nach B.
rueckYesBefund in Richtung B nach A.
gleicher_uebergangYesExakt derselbe Übergang, Aufbau und vergleichbarer Bewegungsablauf dokumentiert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 adds useful domain context — that the two directions are held separately and that the transition must be the same already observed one — but says nothing about what the tool returns or how 'nicht_beobachtet' is treated in the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses with the core operation front-loaded and no filler. The German and English restate the same content, which is mildly redundant but justified as a translation aid for a heavily domain-coded name.

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 three parameters are documented and the operation is bounded, but with no output schema the description should indicate what the agent receives back (a structured confirmation? a classification?). As written, an agent knows what to supply but not what to expect in return.

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% and both enum parameters carry their own descriptions, so the schema does the heavy lifting. The description only reinforces the 'same transition' condition tied to gleicher_uebergang and the direction split behind hin/rueck, adding no syntax or format detail 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 English gloss states a concrete operation: identify direction-specific pauses at the same already observed flooring transition. However, the German lead phrase 'Hält getrennt fest' ('records separately') frames it as a documentation act while the gloss frames it as identification, leaving the actual operation slightly ambiguous. It also gives no hint of how it differs from nearby flooring-evidence siblings such as rollwagen_belagrichtung_marketing_und_eigenbefund.

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 when-to-use or when-not-to-use guidance and no named alternative. The only contextual constraint is implicit in 'am gleichen beobachteten Bodenwechsel', which an agent must interpret on its own to know when this tool rather than a sibling applies.

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