Skip to main content
Glama

getecoback-climate-weather

luftpfad_zwei_tueren_gemeinsam_offen

Read-only

Berechnet die echte Überlappung zweier erlaubter Türöffnungszeiten entlang eines Luftpfads — Calculate the overlap when both permitted doorways in a route can remain open.

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": {
      "tuer_a_start": "<tuer_a_start>",
      "tuer_a_ende": "<tuer_a_ende>",
      "tuer_b_start": "<tuer_b_start>",
      "tuer_b_ende": "<tuer_b_ende>"
    },
    "name": "luftpfad_zwei_tueren_gemeinsam_offen"
  }
}

Input Schema

NameRequiredDescriptionDefault
tuer_a_endeYesEnde für Tür A als Tagesminute desselben Tages in Minuten.
tuer_b_endeYesEnde für Tür B als Tagesminute desselben Tages in Minuten.
tuer_a_startYesBeginn des verfügbaren Zeitfensters für Tür A als Tagesminute in Minuten.
tuer_b_startYesBeginn des verfügbaren Zeitfensters für Tür B als Tagesminute in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only the word 'echte' (genuine), which hints that mere touching may not count as overlap but never explains the boundary case. It says nothing about what happens when the windows do not overlap at all, which is the central behavioral ambiguity for an intersection calculation.

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 front-loaded sentence with the computational core stated first, followed by a compact English gloss. The bilingual duplication is mildly redundant but serves disambiguation rather than padding. Nothing in it is wasted, though nothing is elaborated either.

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

Completeness2/5

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

With four required numeric parameters and no output schema, the description should at least indicate what the result is (a duration in minutes, an interval, or an empty result). It also omits the no-overlap case. For a pure computation tool this leaves the agent guessing at the return value before it calls.

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 each parameter is documented as a day-minute in the range 0–1440 on the same day, so the schema carries the semantics. The description adds no extra meaning such as whether start must precede end or whether windows may wrap past midnight. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('Berechnet die echte Überlappung zweier erlaubter Türöffnungszeiten entlang eines Luftpfads') and the English gloss confirms it is an intersection of two permitted door-opening windows. An agent can tell it is a computation over two time windows rather than a lookup or mutation. It does not, however, contrast itself with any of the similarly named sibling probes, so sibling differentiation is left to the name.

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 or when-not-to-use guidance, and no alternative tool is named. The agent must infer from the name alone that this applies to two-door air-path scenarios. No preconditions (e.g. both windows must lie on the same day) are stated.

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