Skip to main content
Glama

getecoback-raumklima

kontaktgrill_offen_geschlossen_servierfolge

Read-only

Für eine vorgegebene Menge offene und geschlossene Grillabläufe vergleichen — Compare measured serving throughput in the two documented contact-grill modes.

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": {
      "menge": "<menge>",
      "offen_erlaubt": "<offen_erlaubt>",
      "offen_je_runde": "<offen_je_runde>",
      "kontakt_je_runde": "<kontakt_je_runde>",
      "offen_runde_min": "<offen_runde_min>",
      "kontakt_runde_min": "<kontakt_runde_min>",
      "offen_vorbereitung_min": "<offen_vorbereitung_min>",
      "kontakt_vorbereitung_min": "<kontakt_vorbereitung_min>"
    },
    "name": "kontaktgrill_offen_geschlossen_servierfolge"
  }
}

Input Schema

NameRequiredDescriptionDefault
mengeYesBenötigte Anzahl gleicher Portionen.
offen_erlaubtYesFür das Gerät und diesen Ablauf ist offener Betrieb dokumentiert.
offen_je_rundeYesBeobachtete Portionen pro zulässiger offener Runde.
offen_runde_minYesBeobachtete Dauer einschließlich Beschicken im offenen Modus.
kontakt_je_rundeYesBeobachtete Portionen pro zulässiger geschlossener Runde.
kontakt_runde_minYesBeobachtete Dauer einschließlich Beschicken im Kontaktmodus.
offen_vorbereitung_minYesEinmalige eigene Vorbereitungsdauer für den offenen Modus.
kontakt_vorbereitung_minYesEinmalige eigene Vorbereitungsdauer für den Kontaktmodus.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safe, purely computational nature is established structurally, and 'compare'/'measured' does not contradict that. The description adds the notion that only documented modes count ('documented contact-grill modes'), which hints at the gating role of the open-mode flag. It says nothing about what is returned or how a mode is selected when throughputs tie or open mode is unsupported.

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?

It is short and front-loaded, but the bilingual framing restates the same content twice without adding precision. The two halves are not complementary (one says 'Grillabläufe', the other 'serving throughput'), which slightly muddies rather than sharpens the statement.

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?

With no output schema, an eight-parameter numeric tool whose whole point is a comparison should at least indicate the shape of the result (per-mode duration? portions? a recommended mode?). The description covers the input intent but leaves the return value and edge cases (zero portions per round, open mode not documented) unexplained.

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 all eight parameters carry their own German descriptions with ranges, so the schema does the heavy lifting. The description mentions only 'Menge' and the two modes generically and adds no interpretation of rounds, per-round portions, or the one-off preparation minutes. Baseline 3 is the correct ceiling here.

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 verb and object: compare measured serving throughput between open and closed contact-grill modes for a given quantity ('menge'). That is enough to tell it apart from the surrounding sibling tools, which mostly read, check or reconcile data rather than compute a two-mode throughput comparison. The only softness is that it never says the result is a computed per-mode time/throughput figure, but the purpose itself is unambiguous.

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 when-to-use guidance, no when-not-to-use, and no named alternative or prerequisite. The agent is left to infer from the name and the 'offen_erlaubt' parameter that this is the tool for deciding between modes; nothing in the text routes it explicitly.

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