Skip to main content
Glama

getecoback-climate-weather

spueler_alt_neu_abstellflaeche_uebergabefolge

Read-only

Lieferung und vereinbarte Altgeräte-Abholung bei nur einer Abstellfläche auf eine belegte Reihenfolge prüfen — Check whether one staging spot can serve both old and new units.

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": {
      "alt_ab": "<alt_ab>",
      "alt_bis": "<alt_bis>",
      "neu_ab": "<neu_ab>",
      "neu_bis": "<neu_bis>",
      "ersatzflaeche_belegt": "<ersatzflaeche_belegt>"
    },
    "name": "spueler_alt_neu_abstellflaeche_uebergabefolge"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_abYesBeginn der vereinbarten Belegung durch das Altgerät.
neu_abYesFrühester vereinbarter Beginn der Belegung durch das Neugerät.
alt_bisYesBestätigte Freigabe der Fläche nach vereinbarter Altgeräteabholung.
neu_bisYesSpätestes bestätigtes Ende dieser Belegung.
ersatzflaeche_belegtYesIst eine räumlich getrennte, vereinbarte Ersatzfläche verfügbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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. Beyond that the description only restates the scenario; it does not say what the check returns, how overlapping intervals are treated, or what the expected failure condition looks like — notable gaps given there is no output schema.

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?

It is a single compact statement with the scenario constraint front-loaded. The German and English halves are near-duplicates, which is mild redundancy, but nothing else is wasted.

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?

All five required parameters are documented in the schema, so the calling mechanics are covered. But with no output schema and no statement of what a positive or negative result means, an agent must guess how to interpret the response of this moderately complex scheduling check.

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 (alt_ab, alt_bis, neu_ab, neu_bis, ersatzflaeche_belegt) are already documented in the schema. The description adds no per-parameter meaning, such as that the times are minutes-of-day or that ersatzflaeche_belegt changes the verdict — 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 names a concrete check: whether a single staging spot (Abstellfläche) can serve both the new-unit delivery and the agreed old-unit pickup, checked against a booked sequence. That is a specific verb-plus-resource statement an agent can act on, though the outcome of the check (a verdict/overlap result) is not stated and no sibling 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 Guidelines3/5

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

The phrase 'bei nur einer Abstellfläche' communicates the precondition under which this tool applies (only one staging area available), which implicitly scopes usage. However, there is no explicit when-to-use/when-not guidance and no mention of an alternative tool for multi-spot or non-sequential situations.

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