Skip to main content
Glama

getecoback-raumklima

kuehlfach_geteilte_reserve_verbindliche_nachfuellung

Read-only

Eine überlassene gemeinsame Reserve zwischen bereits zugesagter und rücknehmbarer Belegung aufteilen — Separate firm cold-storage reservations from voluntarily releasable extras.

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>",
      "fest_belegt": "<fest_belegt>",
      "optional_belegt": "<optional_belegt>",
      "zugesagter_nachschub": "<zugesagter_nachschub>"
    },
    "name": "kuehlfach_geteilte_reserve_verbindliche_nachfuellung"
  }
}

Input Schema

NameRequiredDescriptionDefault
plaetzeYesBestätigte Plätze für dieselbe Behältergröße im vorgesehenen Fach.
fest_belegtYesDavon fest zugesagte gleichzeitig belegte Plätze.
optional_belegtYesWeitere belegte Plätze, deren Nutzende eine Verlagerung angeboten haben.
zugesagter_nachschubYesVereinbarte neue gleich große Behälter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only and closed-world behavior, so the safety profile is covered. The description adds the conceptual split between firm and releasable capacity, but says nothing about validation rules (e.g., whether the four quantities must sum consistently) or what the tool returns.

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?

A single front-loaded sentence that states the operation before glossing it in English. The bilingual restatement is slightly redundant but not wasteful enough to hurt usability.

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 four-required-parameter computation with no output schema, the description explains the conceptual task but omits the expected result shape and any constraints linking the parameters. It is adequate but leaves meaningful gaps.

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 coverage is 100%, so the parameters are already documented. The description adds a high-level mapping between 'bereits zugesagter' and 'rücknehmbarer' occupancy, but does not explain the arithmetic relationship among the four values beyond what the schema already says.

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 concrete operation (splitting a shared reserve) and names the two categories being separated: already-committed occupancy versus revocable extras. That is enough to distinguish it from generic reserve tools, though it does not explicitly contrast with any sibling.

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 guidance on when to use this tool versus the many sibling reserve tools, no preconditions, and no exclusions. The agent must infer the use case entirely from the operation's wording.

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