Skip to main content
Glama

getecoback-climate-weather

klimageraet_geteilter_ruhetermin_restfenster

Read-only

Bei zwei Hausaufgaben nur die beobachtet ruhige Phase eines bereits geplanten Klimabetriebs freigeben — Find the part of a call that stays outside a measured audible AC phase.

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": {
      "termin_ab_min": "<termin_ab_min>",
      "termin_bis_min": "<termin_bis_min>",
      "laut_ab_min": "<laut_ab_min>",
      "laut_bis_min": "<laut_bis_min>",
      "zusammenhaengend_min": "<zusammenhaengend_min>"
    },
    "name": "klimageraet_geteilter_ruhetermin_restfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
laut_ab_minYesBeobachteter Beginn der am Terminplatz störenden Phase.
laut_bis_minYesBeobachtetes Ende derselben Phase.
termin_ab_minYesBeginn des still geplanten Termins auf gemeinsamer Zeitachse.
termin_bis_minYesEnde des Termins auf derselben Achse.
zusammenhaengend_minYesMindestdauer eines zusammenhängend ruhigen Abschnitts für den Termin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 safety is covered, but the description adds little beyond that. It never says what the tool returns (the remaining quiet window, its boundaries, or nothing when no sufficiently long contiguous segment exists), and there is no output schema to fall back on. For a purely computed overlapping-window operation, the failure/empty case is exactly what the agent needs disclosed and it is absent.

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 definition is short, but the space is used poorly: the German lead-in is confusing ('Bei zwei Hausaufgaben'), and the English half-sentence restates the idea with a different noun ('call' versus 'Klimabetrieb'). The core idea is present but not front-loaded or unambiguous, so brevity does not translate into clarity here.

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?

Five required numeric parameters, no output schema, and abstract interval semantics demand more than a single ambiguous sentence. Nothing is said about the shape of the result, boundary handling, or behavior when no contiguous quiet segment of the required minimum length exists. With no output schema, the description should have carried the return-value burden and it does not.

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%, with each of the five minute-offset parameters individually documented, so the schema does the heavy lifting and the baseline of 3 applies. The description hints at the relationship between the appointment bounds and the noisy-phase bounds but does not add interpretation such as whether the windows may be disjoint, whether inclusive/exclusive boundaries apply, or how zusammenhaengend_min interacts with the result.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does convey a concrete operation: find the portion of a planned AC appointment ('bereits geplanten Klimabetrieb') that falls outside an observed noisy phase, subject to a minimum contiguous length. However, the phrasing 'Bei zwei Hausaufgaben nur ... freigeben' is opaque and mixes German with an English restatement that shifts the object from a time window to 'a call', leaving the agent to reconstruct the actual computation from the schema. It is directionally clear but not crisp enough to be unmistakable next to the many similarly named Klimageraet siblings.

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 statement of when to use this tool versus the sibling tools such as klimageraet_schallzeit_mittel_zwei_phasen or klimageraet_fruehjahrsstart_ruhezeit, and no prerequisites or exclusions. The only contextual hint is the fragment about an 'already planned' AC operation, which implies the appointment must pre-exist but is never stated as a condition. An agent must infer the selection criteria entirely from the name and the five numeric parameters.

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