Skip to main content
Glama

getecoback-climate-weather

haushaltsgeraet_geteilter_arbeitsplatz_pufferzeiten

Read-only

Am gemeinsam genutzten freigegebenen Arbeitsplatz nach einem frühen Rückbau feststellen, ob die nächste Person ihre Zusage vorziehen kann — Test an earlier shared workspace handoff against actual readiness and consent.

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": {
      "bisherige_zusage_ab_min": "<bisherige_zusage_ab_min>",
      "raum_tatsaechlich_frei_min": "<raum_tatsaechlich_frei_min>",
      "neue_person_bereit_min": "<neue_person_bereit_min>",
      "eigener_aufbau_min": "<eigener_aufbau_min>",
      "vorziehen_angenommen": "<vorziehen_angenommen>"
    },
    "name": "haushaltsgeraet_geteilter_arbeitsplatz_pufferzeiten"
  }
}

Input Schema

NameRequiredDescriptionDefault
eigener_aufbau_minYesZusätzliche Minuten für den bereits geklärten eigenen Aufbau.
vorziehen_angenommenYesDie frühere Nutzung ist von beiden freiwillig angenommen.
neue_person_bereit_minYesBestätigter frühester Beginn der Folgeperson.
bisherige_zusage_ab_minYesUnverändert zugesagter Beginn der nächsten Nutzung.
raum_tatsaechlich_frei_minYesBeobachtete Freigabe nach Entfernen der ersten Einrichtung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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, and the description is consistent with a non-mutating check ('feststellen, ob'). It adds that the check weighs observed readiness against both parties' voluntary consent, but says nothing about what a positive/negative outcome means or whether anything downstream is reserved.

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?

A single compact sentence with the decision goal front-loaded, followed by an English paraphrase. The bilingual duplication is slightly redundant but arguably useful, and no sentence is filler.

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?

With five required parameters and no output schema, the definition never says what comes back — a boolean verdict, a slack-in-minutes figure, or a structured recommendation — which matters for a comparison tool. Inputs are otherwise fully covered by the schema, so the gap is real but narrow.

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 coverage is 100%; every parameter (including the 0-1440 minute bounds) is documented in the schema itself. The description only loosely maps 'readiness' and 'consent' onto the inputs without adding unit, ordering, or constraint information, so 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?

The description states a specific operation: determine whether the next person can pull their committed start time forward after an early clearing of the shared workspace, qualified by 'actual readiness and consent'. The German sentence plus English gloss make the evaluated decision explicit, though no sibling tool is named for contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'nach einem frühen Rückbau' (after an early dismantling/handoff) gives a concrete triggering situation for calling the tool, and the readiness/consent qualifiers indicate what must already hold. No explicit when-not conditions or alternative tools are mentioned, so it stops short of full routing guidance.

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