Skip to main content
Glama

getecoback-raumklima

kontaktgrill_uebergabe_rueckstau

Read-only

Bei beobachteten Grilldurchgängen feststellen, ob die Übergabe mehr Behälter abarbeitet, als neu hinzukommen. — Check whether staging output keeps pace with new arrivals between grill rounds.

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": {
      "zuvor_wartende_behaelter": "<zuvor_wartende_behaelter>",
      "neu_hinzugekommen": "<neu_hinzugekommen>",
      "uebergeben": "<uebergeben>",
      "davon_aus_startbestand": "<davon_aus_startbestand>"
    },
    "name": "kontaktgrill_uebergabe_rueckstau"
  }
}

Input Schema

NameRequiredDescriptionDefault
uebergebenYesInnerhalb des Zeitfensters an ihrem vorgesehenen Platz angekommene Behälter.
neu_hinzugekommenYesInnerhalb des Zeitfensters neu zur Übergabe hinzugekommene Behälter.
davon_aus_startbestandYesDavon Behälter, die schon zu Beginn auf Übergabe warteten.
zuvor_wartende_behaelterYesZu Beginn des beobachteten Zeitfensters auf Übergabe wartende Behälter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations already tell the agent this is a safe, closed computation, and "feststellen/check" is consistent with that rather than contradicting it. What is missing is the behavior of the computation itself: the description never says what verdict or value comes back, how the start backlog (davon_aus_startbestand) enters the comparison, or what counts as 'keeping pace' versus falling behind.

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?

The comparison is front-loaded, and the German and English text say the same thing in two short sentences, which is efficient. The cost is that the parallel bilingual restatement repeats information rather than adding detail such as the return value.

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?

This is a pure computation tool with no output schema, so the description still needs to say what it returns, which it does not. A reader cannot tell whether the result is a boolean, a margin, or a rate, and the fourth parameter's effect on the check is unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented in the schema and the baseline is 3. The description does add a little framing by tying the parameters to an observed time window, but it never explains the role of davon_aus_startbestand, the one field whose semantics remain ambiguous.

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 specific check: whether the handover (Übergabe) processes more containers than are newly arriving within an observed grill round. That verb-plus-predicate is concrete enough to separate it from the other kontaktgrill_* tools, which cover counts, sequences, or schedules rather than an inflow-vs-outflow comparison. It loses a point only because it does not explicitly contrast itself 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 Guidelines3/5

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

"Bei beobachteten Grilldurchgängen" implies the precondition: use this when you have observed counts for a time window. However, there is no guidance on when not to use it, no named alternative, and no statement of what to do if the window data is incomplete or the counts are zero.

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