Skip to main content
Glama

getecoback-climate-weather

saugroboter_flur_belegungswechsel_endpunkte

Read-only

Die zwei belegten Flurzeiten vor einer zusammenhängenden, freigegebenen Roboterpassage berücksichtigen — Find a full passage slot between two confirmed household corridor reservations.

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_bis_min": "<a_bis_min>",
      "b_ab_min": "<b_ab_min>",
      "passage_min": "<passage_min>",
      "stop_puffer_min": "<stop_puffer_min>"
    },
    "name": "saugroboter_flur_belegungswechsel_endpunkte"
  }
}

Input Schema

NameRequiredDescriptionDefault
b_ab_minYesBeginn der folgenden Flurbelegung auf derselben Achse.
a_bis_minYesEnde der vorausgehenden Flurbelegung auf einer gemeinsamen Minutenachse.
passage_minYesBeobachtete Durchfahrtszeit einschließlich vorgabegerechter Vorbereitung.
stop_puffer_minYesVereinbarte zusätzliche Minuten vor Beginn der nächsten Belegung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 and the bar is lower, but the description adds nothing behavioural: it does not say what is returned when the gap is too small for passage_min plus stop_puffer_min, whether an error or an empty result occurs, or what units the resulting slot uses. For a pure interval computation with no output schema, that omission is material.

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?

Two sentences, but they are a German/English doublet that says the same thing twice, and the first clause is front-loaded with the least informative phrasing. Nothing is padded beyond the redundancy, but the duplication means one of the two sentences does not earn its place.

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?

This is a four-required-parameter calculation with no output schema, so the description should explain the shape of the answer (start time of the slot? duration? failure mode?). It does not, leaving the agent unable to interpret or validate the result. Only the read-only nature is inferable, and that comes from the annotations, not the text.

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 all four parameters are already documented with bounds (0–1440) and per-field German descriptions; baseline 3 applies. The description only loosely gestures at the two interval endpoints ('die zwei belegten Flurzeiten') and says nothing about how stop_puffer_min interacts with b_ab_min or how passage_min is measured, so it adds no meaning beyond the schema.

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 English half ('Find a full passage slot between two confirmed household corridor reservations') names a concrete operation, but the German preamble is a vague restatement ('die zwei belegten Flurzeiten ... berücksichtigen') rather than a verb stating what is produced. Nothing distinguishes it from near-neighbours like 'lueftung_belegungswechsel_zeitfenster' or 'saugroboter_akkupause_zeitfenster', so an agent must open both schemas to tell them apart.

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?

No statement of when this tool should be chosen, what prerequisites exist (e.g. that both reservations must already be confirmed), or which sibling to use for adjacent scheduling questions. The description only implies usage through the noun 'passage slot'.

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