Skip to main content
Glama

getecoback-raumklima

wasserroute_zwischenablage_fuellgefaesse_puffer

Read-only

Eine Zwischenablage für ankommende und fertig abgeholte Wassergefäße getrennt bilanzieren — Find peak staging demand from known placements and pickups.

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": {
      "plaetze": "<plaetze>",
      "start": "<start>",
      "ankunft_a": "<ankunft_a>",
      "abholung": "<abholung>",
      "ankunft_b": "<ankunft_b>"
    },
    "name": "wasserroute_zwischenablage_fuellgefaesse_puffer"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYesAm Anfang bereits belegte Plätze.
plaetzeYesVor Ort bestätigte getrennte Plätze für die konkret erprobten Gefäße.
abholungYesVor zweiter Ankunft tatsächlich abgeholte Gefäße.
ankunft_aYesGefäße aus erster Ankunft.
ankunft_bYesGefäße aus zweiter Ankunft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 that the operation balances incoming versus picked-up vessels separately and derives a peak demand, which tells the agent this is a deterministic computation rather than storage. It does not disclose the return format, units, or whether the capacity bound implied by 'plaetze' constrains the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short, but it is split across two languages and the German and English clauses largely restate the same idea, so half the text is redundant. The core computation is not front-loaded; it arrives in the second clause.

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 say what value comes back (peak count, time step, unit) and how the ordering of ankunft_a, abholung, ankunft_b is interpreted. It names the goal but leaves the result shape and the sequencing logic unstated, which is a meaningful gap for a pure-calculation tool.

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%, with each of the five parameters documented in the schema itself (start, plaetze, ankunft_a, abholung, ankunft_b). The description adds no parameter-level meaning beyond restating 'placements and pickups', so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The English half ('Find peak staging demand from known placements and pickups') gives a recognizable verb and resource, but the German half ('getrennt bilanzieren') is abstract and the term 'Zwischenablage' is reused across sibling names, so it is unclear whether this stages data or computes a figure. An agent would have to guess that the tool performs a demand calculation rather than storing state. No sibling differentiation is offered.

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?

There is no statement of when to use this tool, when not to, or which sibling (e.g. entfeuchter_tank_zwischenablage_abgleichen) covers an adjacent case. The only hint is the phrase 'from known placements and pickups', which implies inputs but not a usage condition.

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