Skip to main content
Glama

getecoback-climate-weather

haushaltsgeraet_teilen_freie_rueckgabefenster

Read-only

Ein bereits verfügbares Leihgerät vor oder nach einer festen Reservierung einplanen — Find a feasible undivided borrowing slot including handback time.

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": {
      "gemeinsamer_einsatz_belegt": "<gemeinsamer_einsatz_belegt>",
      "frei_ab": "<frei_ab>",
      "frei_bis": "<frei_bis>",
      "block_ab": "<block_ab>",
      "block_bis": "<block_bis>",
      "eigene_dauer": "<eigene_dauer>",
      "rueckgabe_puffer": "<rueckgabe_puffer>"
    },
    "name": "haushaltsgeraet_teilen_freie_rueckgabefenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
frei_abYesTag, ab dem das Gerät im Plan grundsätzlich verfügbar ist.
block_abYesBeginn einer bereits festen Nutzung im Verfügbarkeitsfenster.
frei_bisYesErster Tag außerhalb des gesamten Verfügbarkeitsfensters.
block_bisYesErster Tag nach der bereits festen Nutzung.
eigene_dauerYesZusammenhängende Tage für den eigenen Einsatz.
rueckgabe_pufferYesWeitere Tage für vereinbarte Rückgabe und Pflege.
gemeinsamer_einsatz_belegtYesIst die Nutzung durch alle Beteiligten vereinbart und ist das konkrete Gerät für die geplanten Aufgaben geeignet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 of a pure computation is covered. The description usefully adds that the slot must be 'undivided' and must include handback time, but it never says whether an infeasible schedule yields an error, a null, or a nearest-fit answer — a key behavioral trait for a feasibility solver. It also says nothing about the 'gemeinsamer_einsatz_belegt' precondition being a gate.

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?

Two short clauses with no filler, and the task scenario is stated up front. The German and English phrases largely restate each other, so one of them is close to redundant, but the overall length is well matched to the tool.

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 seven required parameters and no output schema, the description should at least sketch what a returned slot looks like (start/end day, whether the buffer is included), and it does not. The input side is well served by the fully documented schema, so the remaining gap is the result contract for a solver-style tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns above that by explaining that eigene_dauer and rueckgabe_puffer must form one contiguous block and that the block_* parameters represent the fixed reservation the new slot must sit before or after. It does not, however, clarify what the boolean prerequisite parameter does to the computation when false.

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 verb-and-resource outcome — 'Ein bereits verfügbares Leihgerät ... einplanen' / 'Find a feasible undivided borrowing slot including handback time' — and scopes it to before/after a fixed reservation, which is more specific than the name alone. It does not contrast itself with similarly named siblings such as haushaltsgeraet_geteilter_arbeitsplatz_pufferzeiten or haushaltsgeraet_ersatz_unabhaengige_engpaesse, so the differentiation is only partial.

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?

'vor oder nach einer festen Reservierung' implies the situation that selects this tool (scheduling around an existing block), which is implied usage rather than explicit guidance. There is no statement of when not to use it, no mention of what to do when no slot fits, and no pointer to an alternative sibling tool.

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