Skip to main content
Glama

getecoback-raumklima

saugroboter_wischen_nach_trockenauftrag

Read-only

Bei zwei tatsächlichen Aufträgen die bestätigte Umrüstung neben der schon eingeplanten Pause ausweisen. — Budget the verified dry-to-wet changeover separately from idle time.

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": {
      "abstand_min": "<abstand_min>",
      "station_nachlauf_min": "<station_nachlauf_min>",
      "umruesten_min": "<umruesten_min>",
      "boden_und_wechsel_bestaetigt": "<boden_und_wechsel_bestaetigt>"
    },
    "name": "saugroboter_wischen_nach_trockenauftrag"
  }
}

Input Schema

NameRequiredDescriptionDefault
abstand_minYesPause zwischen trockenem Auftrag und geplantem Start der feuchten Reinigung.
umruesten_minYesDanach erforderliche bestätigte aktive Minuten für den vorgesehenen Wechsel.
station_nachlauf_minYesErst abzuwartender beobachteter Stationsnachlauf.
boden_und_wechsel_bestaetigtYesSind die feuchte Reinigung für den Boden und der Wechsel für das genaue Modell geklärt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safety profile is covered. The description adds that only a 'bestätigte' changeover should be budgeted and that it must be shown separately from idle time, which is useful context, but it does not explain the result or how the separate budgeting is represented.

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 description is short and front-loads the condition and action. The appended English translation duplicates the German sentence rather than adding information, which is a minor waste but does not obscure the core instruction.

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 has four fully documented parameters and read-only annotations, so the description need not repeat schema details. It is still incomplete for a planning tool because it does not clarify what is returned or how this budget should be used relative to siblings, and no output schema is present.

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 is already documented in the input schema. The description does not add format, unit, or interpretation details beyond what the schema provides, so the baseline of 3 is appropriate.

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 indicates that the tool budgets a confirmed dry-to-wet changeover separately from an already planned pause, which is a specific domain action rather than a tautology. However, the verb 'ausweisen' is vague and the description does not explicitly distinguish this tool from any of the many sibling robot-vacuum planning tools.

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?

The phrase 'Bei zwei tatsächlichen Aufträgen' implies a condition for use, but the description does not say when to choose this tool over alternatives or when not to use it. No sibling tool is named or contrasted, leaving routing guidance largely absent.

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