Skip to main content
Glama

getecoback-climate-weather

heizwaesche_weitergabe_trockene_teilmasse_vorrang

Read-only

Bereits geprüfte Stücke nach einer eigenen Mengenpriorität entnehmen, ohne feuchte Gruppen rechnerisch gutzuschreiben — Determine if a verified dry subset meets a planned first delivery.

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": {
      "zustand_und_zuordnung_belegt": "<zustand_und_zuordnung_belegt>",
      "prioritaet_g": "<prioritaet_g>",
      "andere_fertig_g": "<andere_fertig_g>",
      "prioritaet_min_g": "<prioritaet_min_g>",
      "andere_darf_ausgleichen": "<andere_darf_ausgleichen>"
    },
    "name": "heizwaesche_weitergabe_trockene_teilmasse_vorrang"
  }
}

Input Schema

NameRequiredDescriptionDefault
prioritaet_gYesTatsächlich am Ziel bestätigte Masse der zuerst benötigten Gruppe.
andere_fertig_gYesWeitere davon getrennte, am Ziel bestätigte Trockenmasse.
prioritaet_min_gYesEigener Mindestbedarf für die erste Übergabe.
andere_darf_ausgleichenYesSind andere trockene Stücke vom Zweck her als Ersatz bestätigt?
zustand_und_zuordnung_belegtYesSind alle Stückgruppen getrennt gewogen und zielgerecht kontrolliert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/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 substantive rule that wet groups may not be offset arithmetically, which is real behavioral context. However, "entnehmen" implies removing/taking pieces, which sits awkwardly against a read-only predicate, and the description never explains the decision logic (priority mass vs. minimum requirement, effect of the boolean substitution flag) or what the call yields.

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?

It is a single tight statement with no filler, and the constraint clause is placed after the main purpose. The German sentence and the English gloss are largely duplicative, which costs a point but does not obscure the message.

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 five-parameter, all-required read-only evaluator with no output schema, the description should either state the return outcome or spell out the decision rule; it does neither. With the schema handling parameter meaning and annotations handling safety, a 3 is defensible, but an agent still cannot predict the result of the call.

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 each of the five parameters carries a precise German definition (e.g. prioritaet_g as 'confirmed at destination mass of the first-needed group'), so the schema already carries the semantics. The description adds no parameter-level meaning beyond it, which is the expected baseline of 3 when coverage is this high.

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 description pairs a German action clause ("Bereits geprüfte Stücke ... entnehmen") with an English gloss ("Determine if a verified dry subset meets a planned first delivery"), which together gesture at a yes/no feasibility check. But the leading verb "entnehmen" reads like a physical extraction while the gloss reads like a predicate evaluation, so the actual operation stays ambiguous. No sibling is named or contrasted, despite ~30 heizwaesche_* siblings.

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 call this rather than any sibling (e.g. heizwaesche_fertige_teile_aus_massenspur_entfernen or heizwaesche_endpunkt_zwischen_zwei_stichproben). The only boundary given is a computational exclusion — wet groups must not be arithmetically credited — which constrains the calculation but does not route the agent between tools.

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