Skip to main content
Glama

getecoback-climate-weather

saugroboter_zwei_raumtermine_reihenfolge

Read-only

Mit beobachteten Fahrzeiten prüfen, in welcher Reihenfolge beide Räume rechtzeitig fertig werden. — Choose the feasible order for two robot-cleaning deadlines.

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": {
      "a_dauer_min": "<a_dauer_min>",
      "b_dauer_min": "<b_dauer_min>",
      "wechsel_min": "<wechsel_min>",
      "a_spaetestens_min": "<a_spaetestens_min>",
      "b_spaetestens_min": "<b_spaetestens_min>"
    },
    "name": "saugroboter_zwei_raumtermine_reihenfolge"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_dauer_minYesBeobachtete Fahrminuten in Raum A.
b_dauer_minYesBeobachtete Fahrminuten in Raum B.
wechsel_minYesBeobachteter Übergang zwischen Räumen in beiden Richtungen.
a_spaetestens_minYesFrist für Raum A in Minuten ab dem gemeinsamen möglichen Start.
b_spaetestens_minYesFrist für Raum B in Minuten ab demselben Start.

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 declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a side-effect-free, closed-world computation. The description adds that travel times are 'observed' and that the transition applies 'in both directions', which is useful. It does not say what the result looks like (the chosen order, feasibility verdict, slack/shortfall), which matters for a pure calculation tool.

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?

Two short sentences, front-loaded with the condition (observed travel times) and the goal (both rooms on time). The German/English duplication is somewhat redundant, but nothing is padded or buried.

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?

Five required numeric parameters and no output schema, so the description should at minimum say what the tool returns (feasible order, and presumably the times or a failure indication). Parameter meaning is fully covered by the schema, but the return semantics are left to inference, which is a real gap for a computation tool.

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 every parameter carries its own German explanation (durations, bidirectional transition, per-room deadline measured from the same start), so the schema does the heavy lifting. The description adds only the framing 'observed travel times' and 'both directions', not per-parameter meaning. 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?

States a concrete verb+resource: it checks, using observed travel times, which order lets both rooms be finished before their deadlines. An agent can tell this is a two-room sequencing feasibility check rather than a plain order-listing tool. It stops short of naming how it differs from the sibling ordering tools (e.g. the pflege_* or saugwischer ordering tools).

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?

Usage is only implied: the mention of 'deadlines' and observed durations signals this applies when two room deadlines must both be met. There is no explicit when-not condition, no statement of what to do when neither order is feasible, and no pointer to an alternative tool.

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