Skip to main content
Glama

getecoback-climate-weather

heissluft_grillrost_lieferumfang_pruefen

Read-only

Für einen geplanten Grillvorgang den vorhandenen Rost mit der dokumentierten Gerätereferenz abgleichen — Check whether a cooking plan relies on a supplied rack or needs accessory confirmation.

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": {
      "variante": "<variante>",
      "grillrost_noetig": "<grillrost_noetig>",
      "rost_vorhanden": "<rost_vorhanden>"
    },
    "name": "heissluft_grillrost_lieferumfang_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
varianteYesGenaue Referenz am Gerät.
rost_vorhandenYesPassender Rost ist mit erkennbarer Zuordnung zum Gerät vorhanden.
grillrost_noetigYesDer gewählte, bereits dokumentierte Ablauf benötigt einen Grillrost.

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 the agent knows this is a safe, closed-world read; the description correctly does not contradict that. What it adds is the decision framing — the result is meant to distinguish 'plan is fine' from 'accessory must be confirmed' — which is useful context beyond the annotations. It says nothing about what the check actually returns, how ambiguity (variante='unbekannt') is resolved, or whether any state is recorded, so it stays at the lower baseline the annotations permit.

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 operative content is front-loaded in the German clause, which is good. However, the description is essentially the same sentence stated twice in German and English without the second version adding detail, which is redundant padding rather than reinforcement. Nothing is unfocused, but the duplication costs it a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, read-only, closed-world verification with no output schema, the description covers the intent and the decision it supports, and the schema carries the parameter detail. The main residual gap is the absence of any hint about the shape of the verdict, but with full schema coverage and clear safety annotations that is a minor omission rather than a blocking one.

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 the three parameters, including the 'variante' enum, are already fully documented in the schema and the description does not need to re-explain them. It loosely echoes two of them ('vorhandener Rost', 'Gerätereferenz') but adds no constraint, format, or interaction rule beyond that — notably nothing on how the two booleans combine. Baseline 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 operation: comparing the rack actually present against the documented device reference ('den vorhandenen Rost mit der dokumentierten Gerätereferenz abgleichen') and judging whether a planned grilling run needs a rack or an accessory confirmation. That is a specific verb plus resource, and the 'Lieferumfang' framing separates it from sibling checks like temperature or zone collision. It stops short of explicitly naming a sibling to contrast against, so it is clear rather than exemplary.

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 clause 'Für einen geplanten Grillvorgang' supplies the operative context: this is a pre-check run while planning a grilling operation. There is no explicit statement of when not to call it, no prerequisites (e.g. that the device reference must already be documented), and no named alternative for cases where the rack question is irrelevant. Usage is implied rather than prescribed.

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