Skip to main content
Glama

getecoback-climate-weather

geraetetransport_wegabschnitt_rollen_oder_griff_nachweis

Read-only

Erfasst welche vorgesehenen Abschnittsarten vom eigenen Beleg über Rollen und Tragegriff überhaupt gedeckt sind — Match documented rolling and carrying evidence to separate route sections.

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": {
      "rollabschnitt_benoetigt": "<rollabschnitt_benoetigt>",
      "trageabschnitt_benoetigt": "<trageabschnitt_benoetigt>",
      "rollunterlage_und_abschnitt": "<rollunterlage_und_abschnitt>",
      "griffunterlage_und_zustand": "<griffunterlage_und_zustand>"
    },
    "name": "geraetetransport_wegabschnitt_rollen_oder_griff_nachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
rollabschnitt_benoetigtYesEin dokumentierter Rollabschnitt gehört zum Vorhaben.
trageabschnitt_benoetigtYesMindestens ein Abschnitt benötigt separat belegtes Tragen.
griffunterlage_und_zustandYesExakte Griffunterlage passt zum dann tatsächlich vorhandenen Aufbau.
rollunterlage_und_abschnittYesExakte Rollenunterlage passt zum vorgesehenen Abschnitt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 that this is a matching/coverage assessment rather than a data fetch, but it never says what the tool returns (no output schema exists) or what happens when supplied booleans conflict with each other. The verb "Erfasst" (records/captures) sits awkwardly next to readOnlyHint, though in context it reads as "determines which are covered" rather than a write.

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 the core claim is front-loaded, but the German sentence and its English restatement do not quite mirror each other ("Erfasst ... gedeckt sind" vs. "Match ... to separate route sections"), which leaves the reader parsing two slightly different propositions rather than one crisp definition.

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 tool whose entire purpose is to produce a verdict, and which has no output schema, the description should explain the shape of the result (per-section coverage? overall verdict?) and the semantics of a partial mismatch. Neither is addressed, so an agent cannot anticipate what it will receive.

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 all four required booleans carry their own German explanations, so the schema already carries parameter meaning. The description adds no per-parameter semantics, so the baseline of 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 pairs a verb with a resource ("Match documented rolling and carrying evidence to separate route sections"), so the subject matter is identifiable, but the German lead-in "Erfasst welche vorgesehenen Abschnittsarten ... überhaupt gedeckt sind" is dense jargon that leaves the actual operation (a coverage check returning per-section-type verdicts) implicit. It does not distinguish itself from the many similar "..._nachweis" siblings listed.

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 statement of when this tool should be chosen over an alternative, no preconditions, and no exclusions. The closest thing to guidance is the phrase "vom eigenen Beleg" (from one's own evidence), which hints at a prerequisite but never states it 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