Skip to main content
Glama

getecoback-climate-weather

roboter_wiederaufnahme_doppelpass

Read-only

Nach einer manuellen Pause doppelt befahrene Abschnitte und ausgelassene Aufgaben erfassen. — Measure repeated segments and skipped work after a manual pause.

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": {
      "abschnitte": "<abschnitte>",
      "vor_pause_erledigt": "<vor_pause_erledigt>",
      "davon_wiederholt": "<davon_wiederholt>",
      "danach_neu_erledigt": "<danach_neu_erledigt>"
    },
    "name": "roboter_wiederaufnahme_doppelpass"
  }
}

Input Schema

NameRequiredDescriptionDefault
abschnitteYesMarkierte Abschnitte der geplanten Route insgesamt.
davon_wiederholtYesBereits fertige Abschnitte, die der Roboter nach der Pause wiederholt hat.
vor_pause_erledigtYesAbschnitte, die vor der Pause fertig waren.
danach_neu_erledigtYesVor der Pause offene Abschnitte, die nach der Pause fertig wurden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that this is a read-only, closed-world operation. The description adds that measurement happens after a manual pause, but it does not explain what result is produced, whether counts are validated for consistency, or how skipped work is derived.

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?

The definition is short and front-loads the operative condition. The German sentence is repeated in English, which is mildly redundant but not harmful.

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 read-only measurement tool with four required numeric inputs and no output schema, the description explains the purpose and timing but not the returned measurement or calculation logic. It is minimally adequate, with room for more behavioral detail.

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 parameter is documented in the schema with clear German labels. The description reinforces the concepts of repeated segments and skipped work, but adds no syntax, constraints, or interpretation beyond the schema.

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 states a specific action in context: measuring repeated route segments and skipped work after a manual pause. It is clear enough to distinguish this from general robot status or service tools, though 'Doppelpass' in the name is opaque and the skipped-work concept is only indirectly reflected in the parameters.

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

Usage Guidelines4/5

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

The phrase 'Nach einer manuellen Pause' gives a clear temporal/operational condition for using the tool. It does not name alternatives or when-not-to-use cases, but the primary usage context is explicit.

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