Skip to main content
Glama

getecoback-raumklima

roboter_service_kartenausschnitt_meldung

Read-only

Eines von zwei bereits vorhandenen Kartenbildern anhand der für eine Fehlermeldung sichtbaren Angaben auswählen — Choose a low-detail evidence crop for a navigation issue.

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": {
      "eng_stoerstelle_sichtbar": "<eng_stoerstelle_sichtbar>",
      "eng_zeit_zugeordnet": "<eng_zeit_zugeordnet>",
      "weit_nur_noetiges": "<weit_nur_noetiges>",
      "weit_stoerstelle_sichtbar": "<weit_stoerstelle_sichtbar>"
    },
    "name": "roboter_service_kartenausschnitt_meldung"
  }
}

Input Schema

NameRequiredDescriptionDefault
weit_nur_noetigesYesDer weitere Ausschnitt zeigt ebenfalls nur die für die Meldung erforderlichen Kartenbereiche?
eng_zeit_zugeordnetYesEngerer Ausschnitt ist dem betroffenen Lauf eindeutig zugeordnet?
eng_stoerstelle_sichtbarYesIm engeren Ausschnitt sind Störstelle und betroffener Streckenabschnitt erkennbar?
weit_stoerstelle_sichtbarYesIm weiteren Ausschnitt sind Störstelle und Streckenabschnitt erkennbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 and the description correctly reinforces that this only picks among pre-existing images. However, with no output schema, the description never states what is returned (an identifier, path, or the selected image itself) or what happens when the booleans conflict, leaving real behavioral gaps.

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?

A single compact sentence, front-loaded with the core action, followed by a short English gloss. The bilingual duplication is slightly redundant but cheap, and there is no filler.

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?

For a four-required-parameter selection tool with no output schema, the definition should explain the selection outcome and the return value; it does neither. The input side is fully documented via the schema, so the gap is confined to the result and decision logic.

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 each of the four booleans carries its own German explanation, so the schema does the heavy lifting. The description adds no decision semantics beyond the schema — notably it never says how eng_* versus weit_* signals are weighed when both sets are true.

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 specific action (selecting one of two existing map images) tied to a concrete context (a fault report / navigation issue), and clarifies that the crops already exist rather than being generated. It does not distinguish this tool from any sibling, but the verb+resource pairing is unambiguous on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase 'für eine Fehlermeldung sichtbare Angaben' — the tool is for evidence selection during fault reporting — but there is no explicit when-to-use statement, no exclusion criteria, and no named alternative. Nothing tells the agent how the four booleans should drive the choice between the narrow and wide crop.

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