Skip to main content
Glama

getecoback-raumklima

haushaltsaufgaben_verteilter_vorrat_teilbar

Read-only

Gemeinsamen zulässigen Nachfüllvorrat ausweisen, wenn zwei vorhandene Bestände nur ihrer jeweiligen Aufgabe dienen — Reserve enough shared refill water after respecting non-transferable supplies.

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": {
      "bedarf_a_l": "<bedarf_a_l>",
      "bedarf_b_l": "<bedarf_b_l>",
      "nur_a_l": "<nur_a_l>",
      "nur_b_l": "<nur_b_l>",
      "flexibel_l": "<flexibel_l>"
    },
    "name": "haushaltsaufgaben_verteilter_vorrat_teilbar"
  }
}

Input Schema

NameRequiredDescriptionDefault
nur_a_lYesSchon vorhandener, ausschließlich für A freigegebener Vorrat.
nur_b_lYesSchon vorhandener, ausschließlich für B freigegebener Vorrat.
bedarf_a_lYesGemessener Wasserbedarf der Aufgabe A.
bedarf_b_lYesGemessener Wasserbedarf von B.
flexibel_lYesVorab geprüfter, beliebig teilbarer Vorrat für beide Aufgaben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 contributes the meaningful behavioral point that non-transferable supplies are respected first before shared refill is reserved, but says nothing about how the result is derived, edge cases where demand exceeds supply, or what is returned.

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?

It is a single short sentence and front-loads the German statement of purpose, which is good. However, the English half largely re-states the same content rather than adding information, and the combined text remains cryptic for a computational tool.

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 five-parameter computation with no output schema, so the description should clarify what the tool returns (presumably a quantity in liters of shared refill supply) and how inputs combine. Neither the return value nor the computation logic is described, leaving a real gap for a tool of this complexity.

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 are already documented in the schema, making the baseline 3. The description echoes the concept of two non-transferable stocks plus a divisible shared reserve but adds no units, bounds, or interpretation beyond the schema.

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 German clause names a verb and resource ("Gemeinsamen zulässigen Nachfüllvorrat ausweisen") plus a precondition (two existing stocks serve only their own task), so the general intent is graspable. But "ausweisen" is vague about whether this computes, reports, or allocates, and nothing distinguishes it from siblings like oskar_filtermatten_gemeinsamer_vorrat or spuelgut_nutzbar_ersatz_vorrat_ausgabefolge.

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?

The only usage signal is the clause "wenn zwei vorhandene Bestände nur ihrer jeweiligen Aufgabe dienen", which merely restates what the nur_a_l/nur_b_l parameters already encode rather than telling the agent when to pick this tool over an alternative. No when-not conditions and no named alternatives are given.

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