Skip to main content
Glama

getecoback-raumklima

saugroboter_drei_kurzauftraege_auswahl

Read-only

Aus drei freiwillig angemeldeten Kurzaufträgen die bis zum gemeinsamen Ende erreichbare Teilmenge bestimmen — Select the largest feasible set of three short robot jobs under one shared deadline.

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_min": "<a_min>",
      "b_min": "<b_min>",
      "c_min": "<c_min>",
      "slot_min": "<slot_min>"
    },
    "name": "saugroboter_drei_kurzauftraege_auswahl"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_minYesBeobachtete Gesamtzeit für Auftrag A einschließlich Rückkehr.
b_minYesBeobachtete Gesamtzeit für Auftrag B einschließlich Rückkehr.
c_minYesBeobachtete Gesamtzeit für Auftrag C einschließlich Rückkehr.
slot_minYesGemeinsames freigegebenes Zeitfenster mit ausreichender vorbereiteter Akkuladung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety profile is covered and the description only needs to add context. It adds that the selection is constrained by a shared deadline and that the answer is a subset, but it does not say what happens when no subset is feasible (empty result?), how ties between equally large feasible sets are broken, or whether job order matters.

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?

Short and front-loaded: the operation and its constraint come first. The only waste is that the English sentence restates the German one verbatim rather than extending it, but the definition is still tight overall.

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?

There is no output schema, so the description carries the burden of describing the return value, and it only gestures at 'the reachable subset' without saying what form that takes (which jobs, in what representation, or an empty result on infeasibility). For a small deterministic four-parameter computation this is adequate but leaves a real gap for correct invocation interpretation.

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 of the four parameters is documented in the schema, so the baseline is 3. The description's reference to 'three short jobs' and 'one shared deadline' maps onto a_min/b_min/c_min and slot_min but adds no interpretation, units, or edge-case semantics beyond what the schema already states.

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 (bestimmen / select) and resource (the feasible subset of three short robot jobs under one shared deadline), which is far more specific than a tautology. An agent can tell this is a feasibility/selection computation over three job durations plus one slot. It stops short of 5 because it never contrasts itself with the many sibling saugroboter_* 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 description implies the situation (three jobs already registered, one common end time) but gives no explicit when-to-use, when-not, or alternative tool to prefer. Nothing tells the agent what to do if the jobs are not voluntarily registered or if more than three jobs exist.

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