Skip to main content
Glama

getecoback-raumklima

saugroboter_kabelroute_vorbereiten

Read-only

Hindernisse am Boden vor dem geplanten Roboterlauf zuordnen — Route around unresolved cords and loose items before a robot run.

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": {
      "lose_kabel": "<lose_kabel>",
      "lose_kleinteile": "<lose_kleinteile>",
      "zone_ausschliessbar": "<zone_ausschliessbar>"
    },
    "name": "saugroboter_kabelroute_vorbereiten"
  }
}

Input Schema

NameRequiredDescriptionDefault
lose_kabelYesLiegen noch lose Kabel im vorgesehenen Bereich?
lose_kleinteileYesLiegen dort Kleinteile oder leicht mitziehbare Gegenstände?
zone_ausschliessbarYesLässt sich der betroffene Bereich nach Modellanleitung verlässlich aus dem Lauf ausnehmen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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. The description adds only the pre-run timing; it does not say what the tool actually produces from the three booleans (a verdict? an exclusion recommendation?) or what happens when zone_ausschliessbar is false, which is the case an agent most needs guidance on.

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 front-loaded, but the German and English clauses are near-duplicates rather than complementary, so roughly half the text is redundant. The em-dash splice also makes the intended action ambiguous.

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 three-required-parameter tool with no output schema and no annotations covering results, the description should explain what the boolean answers lead to. As written, an agent knows the topic but not the outcome or the recommended action after calling it.

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 boolean carries a clear German question, so the schema fully documents the inputs. The description adds no further meaning about how the three answers combine, 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 names a domain (ground obstacles before a planned robot run) but the two halves do not quite agree: the German says obstacles are to be 'zugeordnet' (assigned/classified), while the English says 'route around'. An agent gets the general area but not a crisp verb+resource, and it is not differentiated from siblings such as saugroboter_manuelle_zeit or saugroboter_schwelle_pruefen.

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?

'vor dem geplanten Roboterlauf' implies a pre-run timing window, which is real usage context. There is no statement of when not to use it, no prerequisites, and no pointer to an alternative sibling for related pre-run checks.

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