Skip to main content
Glama

getecoback-raumklima

saugroboter_restaufgaben_verteilen

Read-only

Nach Roboterlauf offen gebliebene Arbeiten für den nächsten manuellen Durchgang erfassen — Reserve separate work for stairs, edges and excluded flooring.

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": {
      "treppen": "<treppen>",
      "nicht_erreichbare_raender": "<nicht_erreichbare_raender>",
      "ausgeschlossene_belaege": "<ausgeschlossene_belaege>"
    },
    "name": "saugroboter_restaufgaben_verteilen"
  }
}

Input Schema

NameRequiredDescriptionDefault
treppenYesTreppen gehören zum Reinigungsziel?
ausgeschlossene_belaegeYesSind Teppiche oder empfindliche Beläge aus der Roboterrunde ausgenommen?
nicht_erreichbare_raenderYesSind sichtbare Ränder außerhalb der erreichbaren Roboterbahn offen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so the definition only needs to add context. It adds the post-run timing and the scope of what is reserved (stairs, edges, excluded flooring), which is useful, but says nothing about what the caller receives or whether reserving has any side effect — 'Reserve separate work' borders on implying state change without confirming it.

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?

A single front-loaded sentence, which is efficient in shape. However, the German clause and the English gloss after the em-dash largely duplicate each other while the substantive gap (what the tool returns) goes unaddressed, so the space is not fully earned.

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 three-boolean, 100%-documented input with no output schema, the agent still lacks a statement of the result — a task list, an allocation, or a summary. Purpose and input scope are covered; the outcome side is left blank, which is the main completeness gap for a tool whose value lies in what it produces.

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 coverage is 100%, so each boolean is already documented in the schema. The description echoes the same three domains (Treppen, Ränder, ausgeschlossene Beläge) without adding interpretation rules, e.g. whether a true value means the area is in scope or excluded. Baseline 3 applies.

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 concrete action and object: it records ('erfassen') work left over after a robot run for the next manual pass, scoped to stairs, edges and excluded flooring. That is specific enough for an agent to recognise the tool, though the verb 'erfassen' sits awkwardly beside the tool name 'verteilen' (distribute), leaving a small doubt about whether tasks are merely listed or assigned.

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?

Timing is implied clearly by 'Nach Roboterlauf' and the target audience ('nächster manueller Durchgang'), so the agent knows when this applies. There is no explicit when-not condition and no pointer to a sibling tool, so the guidance remains implicit rather than routing.

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