Skip to main content
Glama

getecoback-raumklima

balkon_ausweichplatz_lernpause_rueckkehrbudget

Read-only

Eine geplante Pause auf dem geschützten Außenplatz zwischen zwei festen Innenaufgaben unterbringen — Reserve a genuinely usable outdoor break including the return.

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": {
      "erste_aufgabe_bis": "<erste_aufgabe_bis>",
      "weiterarbeit_ab": "<weiterarbeit_ab>",
      "hinaus_min": "<hinaus_min>",
      "rueckkehr_min": "<rueckkehr_min>",
      "pause_min": "<pause_min>",
      "aussenplatz_zur_zeit_geprueft": "<aussenplatz_zur_zeit_geprueft>"
    },
    "name": "balkon_ausweichplatz_lernpause_rueckkehrbudget"
  }
}

Input Schema

NameRequiredDescriptionDefault
pause_minYesEigene gewünschte Dauer der Pause am Platz.
hinaus_minYesBeobachteter Hinweg mit der nötigen Vorbereitung.
rueckkehr_minYesBeobachtete Rückkehr mit vollständigem Wiedereinstieg.
weiterarbeit_abYesUnverschiebbarer Start der nächsten Aufgabe am selben Tag.
erste_aufgabe_bisYesEnde der ersten Innenaufgabe.
aussenplatz_zur_zeit_geprueftYesFreie Nutzung, ausreichender Schatten und persönliche Bedingungen am Platz bestätigt?

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 safety profile is covered. The description adds real behavioral context by insisting the break be 'genuinely usable' and explicitly 'including the return', i.e. travel time counts against the budget. It does not state what the tool returns or what happens when the break cannot be accommodated; the verb 'Reserve'/'unterbringen' also faintly suggests a scheduling action that the read-only annotation rules out, though 'Rueckkehrbudget' makes a calculation reading more plausible.

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, front-loaded sentence that states the constraint before the outcome, with no filler. The German and English halves are near-duplicates, which costs a little space but aids disambiguation of an opaque German tool name.

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 six required parameters and no output schema, the description should indicate what comes back — whether a yes/no feasibility verdict, a computed slack/budget figure, or both. It conveys the intent ('genuinely usable') but not the result shape, so an agent knows when to call it but not what to expect. Adequate but with a clear gap given the tool's arithmetic nature.

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% across all six parameters, so the schema already explains each field (Hinweg, Rueckkehr, Pause, Aufgabenende, Weiterarbeit, Platzprüfung). The description adds only the framing that the return leg is part of the budget, which mostly restates what 'rueckkehr_min' already documents. Baseline 3 is appropriate.

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 specific action ('Eine geplante Pause ... unterbringen' / 'Reserve a genuinely usable outdoor break including the return') on a specific resource (the protected outdoor place, bounded by two fixed indoor tasks). An agent can tell this is a fit/feasibility calculation for a break window rather than a generic scheduler. It stops short of 5 because it never names a sibling or clarifies that the result is a computed budget rather than an actual booking.

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?

The phrase 'zwischen zwei festen Innenaufgaben' implies the prerequisite situation (two fixed indoor tasks with a gap), which is useful context. However, there is no explicit when-to-use/when-not guidance and no pointer to any alternative such as the sibling 'arbeitsplatz_raumwechsel_persoenliche_hitzepause'. Usage must be inferred from the required parameters.

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