Skip to main content
Glama

getecoback-climate-weather

saugroboter_start_ohne_telefon_ersatzplan

Read-only

Einen lokalen Ablauf für einen Roboterlauf ohne verfügbares Telefon planen — Identify documented on-device alternatives when the phone is unavailable.

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": {
      "aufgabe": "<aufgabe>",
      "lokaler_start_belegt": "<lokaler_start_belegt>",
      "lokale_zonenwahl_belegt": "<lokale_zonenwahl_belegt>",
      "lokale_pause_belegt": "<lokale_pause_belegt>"
    },
    "name": "saugroboter_start_ohne_telefon_ersatzplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufgabeYesGewünschte Aktion bei fehlendem Telefon.
lokale_pause_belegtYesVor-Ort-Pause ist für das Modell nach Anleitung nachgewiesen?
lokaler_start_belegtYesHandbuch oder erfolgreicher Test belegt ausdrücklich einen lokalen Start für die ganze vorbereitete Fläche?
lokale_zonenwahl_belegtYesDer konkrete Gerätezugang ermöglicht die vorgesehene Zonenwahl vor Ort?

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It does add that the tool works from documented on-device evidence, but it never says what the agent gets back (a plan, a verdict, a refusal) or how the three 'belegt' booleans gate the result. Useful but thin beyond the annotations.

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 front-loaded sentence that puts the core action first. The English half-sentence is largely a translation of the German and adds little, but there is no padding or filler beyond that.

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?

The tool is a closed-world, read-only planning/assessment call with four required parameters and no output schema, so the description should clarify what a plan or verdict looks like and how unmet evidence is reported. It conveys the domain and trigger but leaves the return semantics and the failure/fallback behavior unstated.

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%, so every parameter (including the enum values 'alles_saugen', 'bestimmte_zone', 'pause') is already documented in the schema. The description adds no further meaning about how the three evidence booleans interact or what happens when one is false. Baseline 3 is appropriate.

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 verb+resource: planning a local procedure ('lokalen Ablauf ... planen') for a robot run when no phone is available, and adds that it identifies documented on-device alternatives. An agent can grasp the intent without the schema. It stops short of differentiating from the many sibling saugroboter_* tools, so it falls short of a 5.

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?

The triggering condition is implied clearly ('ohne verfügbares Telefon' / 'when the phone is unavailable'), which tells the agent when this tool is relevant. There is no explicit when-not guidance and no named alternative for the case where a phone IS available, so usage is inferred rather than directed.

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