Skip to main content
Glama

getecoback-climate-weather

pflege_packen_nach_eigenen_pruefpunkten

Read-only

Zusammen gehörende Teile erst nach ihren getrennten Kontrollen zu einem Pflegeset packen — Determine the earliest pack-up time when each component has a separate check.

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": {
      "packen_belegt": "<packen_belegt>",
      "a_geprueft_ab": "<a_geprueft_ab>",
      "b_geprueft_ab": "<b_geprueft_ab>",
      "c_geprueft_ab": "<c_geprueft_ab>",
      "packen_bis": "<packen_bis>"
    },
    "name": "pflege_packen_nach_eigenen_pruefpunkten"
  }
}

Input Schema

NameRequiredDescriptionDefault
packen_bisYesGewünschter spätester Beginn des Packens.
a_geprueft_abYesFrüheste eingeplante Kontrolle für Teil A.
b_geprueft_abYesFrüheste eingeplante Kontrolle für Teil B.
c_geprueft_abYesFrüheste eingeplante Kontrolle für Teil C.
packen_belegtYesIst die geplante Verpackung nach der Vorgabe erlaubt, und sind die Prüfpunkte für genau diese Gruppe dokumentiert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 adds the useful framing of a pure scheduling computation and hints that the result is an earliest feasible pack time, but it does not say what happens when the packen_belegt precondition is false, whether the answer is a time, a failure, or a sentinel value — a notable gap given there is no output schema.

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?

The definition is short and front-loads the constraint (checks must precede packing), which is good. However, the German sentence and the English gloss restate the same content rather than complementing each other, so roughly half the text is redundant.

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-required-parameter computation with no output schema, the description does at least signal the return value (an earliest pack-up time), which is valuable. It remains incomplete about the meaning of a false packen_belegt, edge cases where no feasible time exists, and how the maximum-time domain (0–1440) should be interpreted.

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 (three component check times, a latest pack start, and the packen_belegt eligibility flag) are already documented in the schema with units and bounds. The description adds no extra semantics beyond the schema — no explanation of how check times combine, or how packen_belegt interacts with the returned time — so the baseline of 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 computation — determining the earliest pack-up time for a care set once each component has passed its own separate check — and the German/English pair makes the intent unambiguous. It is specific about verb and resource, but it never situates itself against the numerous sibling scheduling/state tools, so an agent must infer the boundary on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scenario (pack only after per-part checks, bounded by a desired latest pack start) implies when the tool applies, but there is no explicit 'use this when…' statement, no exclusions, and no named alternative among the many siblings. Guidance is inferable rather than stated.

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