Skip to main content
Glama

getecoback-raumklima

pflege_ersatzkorb_vor_leerfahrt_entlasten

Read-only

Zwei getrennte verwendete Sammelkörbe auf eine bestätigte Entleerungsrunde verteilen — Reserve separate room for two used-item groups on the same planned trip.

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": {
      "separate_kapazitaeten_belegt": "<separate_kapazitaeten_belegt>",
      "gruppe_a": "<gruppe_a>",
      "gruppe_b": "<gruppe_b>",
      "a_je_fahrt": "<a_je_fahrt>",
      "b_je_fahrt": "<b_je_fahrt>",
      "runden": "<runden>"
    },
    "name": "pflege_ersatzkorb_vor_leerfahrt_entlasten"
  }
}

Input Schema

NameRequiredDescriptionDefault
rundenYesBis zur geplanten Leerung verfügbare Runden.
gruppe_aYesEindeutig zugeordnete Teile der ersten Gruppe.
gruppe_bYesEindeutig zugeordnete Teile der zweiten Gruppe.
a_je_fahrtYesGeeignete Plätze der ersten Gruppe je Runde.
b_je_fahrtYesGeeignete Plätze der zweiten Gruppe je Runde.
separate_kapazitaeten_belegtYesSind die Fächer getrennt und für ihre jeweilige Gruppe beim Transport geeignet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that this is a read-only, closed-world operation. The description adds contextual constraints such as 'bestätigte Entleerungsrunde' and 'getrennte verwendete Sammelkörbe', but it does not clarify what the computation returns or what happens when the groups cannot be distributed.

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?

The definition is short and front-loaded, with the German statement followed by an English gloss. There is little wasted text, though the bilingual version slightly lengthens an already terse definition.

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?

For a six-parameter read-only calculation tool with no output schema, the description should explain what result the agent will receive. It states the purpose but not whether the tool returns a feasibility result, an allocation, or required rounds, leaving a significant gap.

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 the individual parameters are already documented in the schema. The description loosely maps 'zwei getrennte ... Sammelkörbe' to the two groups and 'bestätigte Entleerungsrunde' to the rounds, but adds no allocation rules or interpretation beyond that.

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 gives a specific verb and resource: 'Zwei getrennte verwendete Sammelkörbe auf eine bestätigte Entleerungsrunde verteilen' / 'Reserve separate room for two used-item groups on the same planned trip'. It is clear enough at a high level, though it does not distinguish itself from any sibling tool.

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 description supplies no explicit when-to-use guidance, no exclusions, and no named alternatives. It implies a planning scenario with two used-item groups and a confirmed emptying round, but the agent is left to infer when this tool should be selected.

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