Skip to main content
Glama

getecoback-raumklima

flexiclip_ein_paar_zwei_kalte_zeitfenster

Read-only

Zwei zur Wahl stehende Zeitfenster von der Angabe gleichzeitig verfügbarer FlexiClip-Paare trennen — Determine whether the logged tasks actually need simultaneous coverage.

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": {
      "plan_fuer_dieses_geraet_belegt": "<plan_fuer_dieses_geraet_belegt>",
      "ebene_a": "<ebene_a>",
      "ebene_b": "<ebene_b>",
      "a_ende_min": "<a_ende_min>",
      "b_beginn_min": "<b_beginn_min>",
      "eigener_wechselpuffer_min": "<eigener_wechselpuffer_min>"
    },
    "name": "flexiclip_ein_paar_zwei_kalte_zeitfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
ebene_aYesVorgesehene Ebene der ersten Aufgabe.
ebene_bYesVorgesehene Ebene der zweiten Aufgabe.
a_ende_minYesErste Tagesminute nach der Nutzung A.
b_beginn_minYesErste Tagesminute der Nutzung B.
eigener_wechselpuffer_minYesFür die belegte kalte Zwischenphase vom Nutzer benötigte Minuten, ohne Geräte- oder Temperaturmodell.
plan_fuer_dieses_geraet_belegtYesSind gewünschte Ebenen und erlaubte getrennte kalte Nutzung beziehungsweise ein zulässiger Wechsel dokumentiert?

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 safety profile is covered. The description adds that the tool evaluates/separation of alternative windows rather than performing a mutation, but it does not disclose the return value, decision semantics, or what happens when the documented-plan boolean is false.

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?

The description is short and front-loads the central operation before the English clarification. The bilingual duplication is slightly redundant, but no sentence is wasted and the structure is easy to scan.

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 six required parameters, full schema descriptions, and read-only annotations, the definition covers the invocation basics. However, for a decision tool with no output schema, the description does not state what the determination returns or how the boolean plan input affects the result, leaving a meaningful gap.

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 six parameters are already well documented in the schema. The description adds the notion that the two windows are alternatives and that simultaneous FlexiClip-pair availability is involved, but it does not explain the individual parameters beyond what the schema provides.

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: separating two alternative time windows from a statement of simultaneously available FlexiClip pairs, and the English gloss clarifies the goal as determining whether logged tasks need simultaneous coverage. It is clear enough to distinguish the tool from generic scheduling tools, though it does not explicitly name a sibling alternative and the German compound phrasing is somewhat opaque.

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 phrase 'Determine whether the logged tasks actually need simultaneous coverage' implies the decision context for using the tool, but there is no explicit when-to-use versus when-not guidance and no named alternative among the many sibling tools. Usage is inferable from the purpose, not stated as routing guidance.

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