Skip to main content
Glama

getecoback-raumklima

wassergefaess_leergut_fuellrunde_bestandsgrenze

Read-only

Vor einer Nachfüllrunde fehlende passende Leergefäße für zwei getrennte Verwendungen erkennen — Count missing returned vessels by their designated use.

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": {
      "a_benoetigt": "<a_benoetigt>",
      "b_benoetigt": "<b_benoetigt>",
      "a_leer_zurueck": "<a_leer_zurueck>",
      "b_leer_zurueck": "<b_leer_zurueck>",
      "unzugeordnet": "<unzugeordnet>"
    },
    "name": "wassergefaess_leergut_fuellrunde_bestandsgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_benoetigtYesFür Zweck A zur Nachfüllung benötigte, vorher eindeutig zugeordnete Gefäße.
b_benoetigtYesFür Zweck B benötigte Gefäße.
unzugeordnetYesZusätzlich vorhandene Gefäße ohne bestätigte Zuordnung.
a_leer_zurueckYesVor Beginn passend zurückgekehrte leere Gefäße für A.
b_leer_zurueckYesPassend zurückgekehrte Gefäße für B.

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 is fully covered by structured data. The description adds that the computation is split by designated use, but it never says what the operation returns (two deficits? one combined number?) or how the 'unzugeordnet' bucket affects the result. With annotations carrying the mutation/access burden, this is an acceptable but thin addition.

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 compact sentences with the purpose front-loaded and the English gloss serving as a clarification rather than padding. The bilingual restatement is slightly redundant but cheap, and there is no wasted preamble.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a derived-value computation with five required inputs and no output schema, so the description must carry the burden of explaining the result — and it does not. An agent cannot tell from the text whether the tool returns two per-use deficits, a single total, or also accounts for the unassigned vessels, which is exactly the ambiguity the 'unzugeordnet' parameter raises.

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% and all five parameters carry German descriptions, so the input schema already explains the meaning of a_benoetigt, b_benoetigt, a_leer_zurueck, b_leer_zurueck and unzugeordnet. The description adds no additional semantics about how those inputs are combined. Baseline 3 applies when the schema does the heavy lifting.

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 computation and scope: detect/count missing matching empty vessels for two separate uses ahead of a refill round ('fehlende passende Leergefäße für zwei getrennte Verwendungen erkennen'). It conveys the resource (empty vessels), the split by designated use, and the timing (before refilling). It does not name any sibling, but none of the listed siblings appears to collide with this purpose.

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?

'Vor einer Nachfüllrunde' gives an explicit situational trigger for when this tool applies, which is useful guidance for an agent. It stops short of stating exclusions (e.g., what to do if assignments are not yet confirmed) or pointing to any alternative tool, so it sits at clear-context-but-no-alternatives.

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