Skip to main content
Glama

getecoback-raumklima

heissluft_rost_entnahme_ablage_nachlauf

Read-only

Die zeitliche Überschneidung der vorgesehenen Rostablage mit dem später geplanten Küchenplatz erkennen. — Check whether a compatible heat-resistant rack rest is occupied when the next task needs it.

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": {
      "rost_ablage_bestaetigt": "<rost_ablage_bestaetigt>",
      "rost_belegt_ab_min": "<rost_belegt_ab_min>",
      "rost_belegt_bis_min": "<rost_belegt_bis_min>",
      "folgeaufgabe_ab_min": "<folgeaufgabe_ab_min>"
    },
    "name": "heissluft_rost_entnahme_ablage_nachlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
rost_belegt_ab_minYesBeobachteter Beginn der Belegung durch den Rost auf der Minutenachse.
folgeaufgabe_ab_minYesGewünschter Zeitpunkt für dieselbe Ablage, auf derselben Achse.
rost_belegt_bis_minYesBeobachteter Zeitpunkt, zu dem die Ablage nach Vorgaben wieder frei war.
rost_ablage_bestaetigtYesIst diese Ablage für Zubehör und Nutzung nach beiden Anleitungen zulässig?

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 and scope are covered and the description need not repeat them. It does add useful behavioral framing — the comparison is between an observed occupancy window and a later planned demand time on the same minute axis. However, it never states what the check yields (a boolean verdict, an overlap interval, or which field carries the answer), and there is no output schema to fill that gap.

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 single core sentence is front-loaded and appropriately short, but the description is effectively duplicated verbatim across German and English, so half the text carries no additional information. The German clause 'mit dem später geplanten Küchenplatz' is also vaguer than the English 'rack rest is occupied', leaving the agent to reconcile two slightly different framings.

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 four required parameters fully documented and readOnly/closed-world annotations present, most of the calling contract is already covered by structured data. The remaining burden on the description — explaining what an overlap check returns, since no output schema exists — is not met, which is a real gap for a pure decision tool whose only value is its verdict.

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 every parameter (rost_ablage_bestaetigt, rost_belegt_ab_min, rost_belegt_bis_min, folgeaufgabe_ab_min) is already documented in the schema and the baseline of 3 applies. The description adds no further meaning about, for example, the 0–1440 minute axis shared by three parameters or how the boolean gate interacts with the overlap computation.

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 operation — detecting a temporal overlap between an observed rack-rest occupancy interval and the desired time of a follow-up task — rather than restating the tool name. An agent can tell this is a conflict/overlap check, not a mutation or lookup. It stops short of naming any sibling tool it should be preferred over, so sibling differentiation is only implicit via the 'Küchenplatz' framing.

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?

Usage is only implied: clause 'when the next task needs it' signals the planning context in which the check applies, and the 'vorgesehene Rostablage' phrase implies a planned-rest scenario. There is no explicit when-not guidance, no prerequisites (e.g. that the rack must first be confirmed permissible), and no named alternative among the many heat-related siblings.

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