Skip to main content
Glama

getecoback-climate-weather

geraetefolge_teilpuffer_nach_lieferung

Read-only

Zwei Gerätedurchgänge gegen einen konkret belegten Zwischenbestand und die nächste gleichartige Nachlieferung prüfen — Test a staged production buffer while keeping both timed resource commitments visible.

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": {
      "puffer_anfang": "<puffer_anfang>",
      "a_entnimmt": "<a_entnimmt>",
      "neu_nach_a": "<neu_nach_a>",
      "b_entnimmt": "<b_entnimmt>",
      "mindestrest": "<mindestrest>"
    },
    "name": "geraetefolge_teilpuffer_nach_lieferung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_entnimmtYesGemessener Bedarf für die erste Aufgabe.
b_entnimmtYesGemessener Bedarf für die zweite Aufgabe.
neu_nach_aYesVerlässlich nach A und vor B ankommende weitere Einheiten.
mindestrestYesVereinbarter Mindestbestand nach der zweiten Aufgabe.
puffer_anfangYesNutzbare Einheiten am Anfang.

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that both timed resource commitments stay visible during the check, which is useful behavioral framing, but it never says what the check returns (feasibility verdict? residual buffer?), and with no output schema that is a real gap.

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?

Two clauses are front-loaded with the scenario, which is good, but the English sentence largely restates the German one rather than adding information, and the phrasing ('keeping both timed resource commitments visible') is abstract filler compared to a concrete statement of what is computed.

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 closed-world read-only computation with five fully documented numeric inputs, the gaps are the missing description of the result and any hint about how the two commitments interact. The annotations and schema carry most of the burden, but without an output schema the description should have said what comes back.

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% and each of the five numbers carries a clear German description (measured demand, reliably arriving units, agreed minimum remainder). The prose contributes no additional parameter meaning beyond the schema, so baseline 3 applies.

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 concrete operation (prüfen/test) over a specific resource pair: two Gerätedurchgänge checked against a documented Zwischenbestand plus the next gleichartige Nachlieferung. The bilingual gloss makes the intent legible, though it never differentiates this task from the many similarly named sibling drills, so an agent must rely on the param names to disambiguate.

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 choose this over any sibling, no exclusion, and no prerequisite. The only contextual cue is 'staged production buffer with next similar delivery,' which implies the scenario but leaves the agent to infer selection criteria entirely.

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