Skip to main content
Glama

getecoback-raumklima

fensterbehang_winter_lichtgewinn_zwei_bloecke

Read-only

Offene Zeit für Tageslicht in zwei geplanten Winter-Nutzungsblöcken prüfen — Check actual daylight access in two separately planned use blocks.

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": {
      "offen_ab": "<offen_ab>",
      "offen_bis": "<offen_bis>",
      "a_ab": "<a_ab>",
      "a_bis": "<a_bis>",
      "a_ziel": "<a_ziel>",
      "b_ab": "<b_ab>",
      "b_bis": "<b_bis>",
      "b_ziel": "<b_ziel>"
    },
    "name": "fensterbehang_winter_lichtgewinn_zwei_bloecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_abYesBeginn Block A.
b_abYesBeginn Block B.
a_bisYesEnde Block A.
b_bisYesEnde Block B.
a_zielYesEigener Mindestbedarf offener Minuten in A.
b_zielYesEigener Mindestbedarf offener Minuten in B.
offen_abYesStart der geplanten Öffnung, Minuten seit Mitternacht.
offen_bisYesEnde der geplanten Öffnung.

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 the safety profile is covered. Beyond that the description discloses nothing: not what happens when a target (a_ziel/b_ziel) is unmet, whether daylight hours are assumed constant, or what the response contains. With no output schema, that omission is material.

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?

It is short and front-loaded, which is good, but it spends half its length on a near-literal English echo of the German sentence rather than adding information. Two languages carrying identical, still-vague content is redundancy, not clarity.

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?

Eight required numeric parameters, no output schema, and an unexplained computation model make this a complex tool, yet the description explains neither the calculation nor the result shape. An agent could fill in the numbers but could not predict or interpret the output.

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 all eight parameters are documented in the schema itself, and the baseline of 3 applies. The phrase 'two separately planned use blocks' loosely maps to the A/B parameter families, but the description adds no semantics about how the four open-window minutes and the two Ziel values interact.

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 names the act ('prüfen' / 'check') and the domain (daylight access across two planned winter use blocks), which is more than a restatement of the name. But it never states what is actually computed or compared — no input for a daylight window is described anywhere, so an agent cannot tell whether the tool returns minutes of overlap, a pass/fail, or a shortfall. The bilingual duplication adds no extra specification.

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 versus the many sibling tools dealing with time blocks, quotas, or room scheduling, and no prerequisites or exclusions. 'In two separately planned use blocks' hints at the A/B structure but gives no selection guidance an agent could act on.

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