Skip to main content
Glama

getecoback-raumklima

roboter_nacharbeit_ersatzroute

Read-only

Die manuelle Ersatzrunde nach einer ausgelassenen Roboterzone auf ein Zeitfenster zuschneiden. — Fit manual backup work after a skipped robot zone into a time slot.

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": {
      "prioritaetsstellen": "<prioritaetsstellen>",
      "gesamtstellen": "<gesamtstellen>",
      "minuten_pro_stelle": "<minuten_pro_stelle>",
      "zeitfenster_minuten": "<zeitfenster_minuten>"
    },
    "name": "roboter_nacharbeit_ersatzroute"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamtstellenYesAlle offenen und für die Ersatzrunde vorgesehenen Stellen.
minuten_pro_stelleYesFür eine vergleichbare Stelle gemessene Minuten von Hand.
prioritaetsstellenYesOffene Pflichtstellen laut eigener Planung.
zeitfenster_minutenYesHeute verfügbares Zeitfenster für die Nacharbeit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 and the description need not repeat it. What the description fails to disclose is the actual behavior: whether priority stations (prioritaetsstellen) are served first, whether the window is truncated, whether an over-capacity input yields a reduced plan or an error. For a pure calculation tool with no output schema, that silence is a real gap.

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 with no filler, and the triggering condition is front-loaded. The only waste is the full bilingual duplication, which roughly doubles the length for no informational gain.

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?

Four required numeric parameters and no output schema mean the definition carries full responsibility for explaining the computation and its result, and it does neither. Nothing tells the agent how the inputs combine, what the returned value represents, or what happens at the schema's edge values (0 minutes, 1000 stations).

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 cryptic German field names are documented in the schema itself (open stations, minutes per station, mandatory priority stations, available window). The description adds no interpretation beyond the schema, so the baseline of 3 applies rather than anything higher.

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 concrete action ('Ersatzrunde ... zuschneiden' / 'fit ... into a time slot') and a concrete trigger ('nach einer ausgelassenen Roboterzone'), so the domain is identifiable. But it largely restates the tool name in two languages and never states what the tool actually produces or computes (a station count? a trimmed list? a feasibility verdict). An agent cannot tell what the outcome of 'fitting' is.

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, no prerequisites (e.g. that a robot zone was actually skipped today), and no reference to alternatives such as roboter_tuerfreigabe_nachholrunde or roboter_wiederaufnahme_doppelpass. The agent must infer the triggering situation from the German noun phrase alone.

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