Skip to main content
Glama

getecoback-raumklima

haushaltsgeraete_zeitversatz_teilzustellung

Read-only

Bei gemeinsamer Aufgabe mit erst später verfügbarem Zwischenprodukt ausweisen, wie viele Teile das Folgegerät rechtzeitig bearbeiten kann — Schedule a second-stage batch with a separate confirmed partial release.

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": {
      "erste_charge_um_min": "<erste_charge_um_min>",
      "erste_charge_stueck": "<erste_charge_stueck>",
      "rest_charge_um_min": "<rest_charge_um_min>",
      "rest_charge_stueck": "<rest_charge_stueck>",
      "je_stueck_min": "<je_stueck_min>",
      "frist_min": "<frist_min>"
    },
    "name": "haushaltsgeraete_zeitversatz_teilzustellung"
  }
}

Input Schema

NameRequiredDescriptionDefault
frist_minYesGewünschter Fertigzeitpunkt auf derselben Achse.
je_stueck_minYesBeobachtete Zeit je Stück im festen zweiten Ablauf.
rest_charge_stueckYesZahl der später verfügbaren Stücke.
rest_charge_um_minYesSpäterer bestätigter Zeitpunkt für die übrigen Stücke.
erste_charge_stueckYesZahl der an diesem ersten Zeitpunkt tatsächlich nutzbaren Stücke.
erste_charge_um_minYesZeitpunkt, zu dem ein Teil vollständig für den zweiten Schritt freigegeben ist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 and scope are covered. The description adds the partial-release scenario but does not clarify the return value (count vs. schedule), calculation assumptions, or handling of infeasible inputs. 'Schedule' is potentially misleading for a read-only computation, though not a direct contradiction.

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 front-loaded sentence with the scenario first, which is efficient. The German and English halves are somewhat redundant, and the English paraphrase introduces mild ambiguity, but overall there is little wasted text.

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 six-required-parameter calculation with no output schema, the description identifies the core computation but leaves the return form and edge-case behavior implicit. The rich schema compensates for parameter documentation, but output expectations remain under-specified.

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 six parameters are already documented with bounds and meanings. The description does not add parameter-level detail beyond the schema; baseline 3 is appropriate.

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 states a specific calculation: determine how many parts the follow-on device can process in time given a later-available intermediate product. The German clause is reasonably precise about the scenario and output quantity, though the English paraphrase 'Schedule a second-stage batch' is less exact and no sibling tool is differentiated.

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 opening condition ('Bei gemeinsamer Aufgabe mit erst später verfügbarem Zwischenprodukt') implies when the tool applies, but there is no explicit when-not guidance or named alternative. Usage is inferable from the scenario rather than clearly routed.

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