Skip to main content
Glama

getecoback-raumklima

heissluft_zonen_handgriff_kollision

Read-only

Je einen notwendigen Bediengriff zweier Programme für eine einzelne Person auf Überschneidung prüfen — Check whether one operator can perform both time-sensitive basket actions.

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": {
      "a_frueh_min": "<a_frueh_min>",
      "a_spaet_min": "<a_spaet_min>",
      "a_dauer_min": "<a_dauer_min>",
      "b_frueh_min": "<b_frueh_min>",
      "b_spaet_min": "<b_spaet_min>",
      "b_dauer_min": "<b_dauer_min>"
    },
    "name": "heissluft_zonen_handgriff_kollision"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_dauer_minYesEigene beobachtete Dauer des Bediengriffs A.
a_frueh_minYesErster zulässiger Beginn des Bediengriffs A laut eigenem Ablaufplan.
a_spaet_minYesSpätester zulässiger Beginn von A.
b_dauer_minYesEigene beobachtete Dauer des Bediengriffs B.
b_frueh_minYesErster zulässiger Beginn des Bediengriffs B.
b_spaet_minYesSpätester zulässiger Beginn von B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safe, local nature of the call is covered. The description adds the framing that the check is scoped to a single operator performing both actions, but says nothing about how overlap is judged (pure interval intersection vs. sequencing vs. duration-derived end times) or what the response looks like.

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?

A single compact sentence with the German statement front-loaded and an English gloss following. The bilingual restatement is mildly redundant but small, and no other wording is wasted.

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 computational tool with no output schema, the description covers the intent but omits the shape of the result and edge-case semantics (touching boundaries, zero durations, whether durations must fit within the windows). Adequate to attempt a call, but not complete enough to predict the 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% — each of the six window/duration parameters carries its own German description, so the schema does the heavy lifting. The description adds only the implicit constraint that both actions share one operator; it does not explain how früh/spät/dauer interact to determine feasibility.

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 verb (prüfen/check) and a specific resource (whether one operator can perform two time-sensitive actions), so an agent knows this is a pairwise feasibility/overlap check rather than a lookup. It does not, however, disambiguate from sibling overlap-style tools or clarify whether the result is a boolean or a schedule, and the jargon ('Bediengriff', 'Programme', 'basket actions') leaves the domain slightly opaque.

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 explicit when-to-use, when-not-to-use, or alternative named. The phrase 'time-sensitive' hints at context but gives no condition for choosing this tool over a sibling such as a validity-window overlap check.

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