Skip to main content
Glama

getecoback-climate-weather

badezimmer_gemeinsame_nutzung_drei_mindestslots

Read-only

Bei drei freiwilligen Badterminen nur die von allen akzeptierte Mindestverkürzung einsetzen — Fit three bathroom bookings by reducing only time explicitly offered for release.

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": {
      "gesamt_geplant_min": "<gesamt_geplant_min>",
      "frei_min": "<frei_min>",
      "a_bietet_min": "<a_bietet_min>",
      "b_bietet_min": "<b_bietet_min>",
      "c_bietet_min": "<c_bietet_min>"
    },
    "name": "badezimmer_gemeinsame_nutzung_drei_mindestslots"
  }
}

Input Schema

NameRequiredDescriptionDefault
frei_minYesTatsächlich verfügbare gemeinsame Zeit.
a_bietet_minYesVon A bereits freiwillig zur Kürzung freigegebene Minuten.
b_bietet_minYesVon B bereits freiwillig zur Kürzung freigegebene Minuten.
c_bietet_minYesVon C bereits freiwillig zur Kürzung freigegebene Minuten.
gesamt_geplant_minYesAddierte Dauer der drei nacheinander geplanten Badtermine inklusive Übergaben.

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 safety is covered. The description adds a genuinely useful behavioral guarantee — that only explicitly offered minutes may be cut, never unilaterally — but says nothing about feasibility outcomes, allocation order, or what the result contains.

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?

One compact sentence with the governing constraint front-loaded; the bilingual duplication is conventional rather than harmful. Nothing superfluous, though the double rendering halves the information density per word.

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 five-required-parameter computation with no output schema, the description should indicate what the tool returns (a fitted duration, per-person reductions, or an infeasibility signal). It covers the input side adequately but leaves the result shape to inference.

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 five parameters are already documented in the schema. The description's 'freiwillig' and 'von allen akzeptierte' wording reinforces the offer semantics but adds no units, bounds, or edge-case meaning beyond the schema.

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 operation (fit three bathroom bookings) and a precise constraint (reduce only minutes explicitly offered for release). The verb 'einsetzen' is a little soft, but the resource and the fitting rule are unambiguous, so an agent can tell this is a three-party scheduling-fit computation rather than a lookup or mutation.

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?

Usage is only implied by the scenario of three voluntary booking offers; there is no statement of when to choose this over the many sibling fit/scheduling tools, no prerequisites, and no guidance on what to do when the offered minutes are insufficient.

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