Skip to main content
Glama

getecoback-raumklima

fassadenbeschattung_zeitfenster_ueberlappung

Read-only

Für die beobachtete Sonnenzeit an der Fassade die nicht beschatteten Minuten bestimmen — Compare one observed direct-sun interval with the planned shade schedule.

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": {
      "sonne_ab": "<sonne_ab>",
      "sonne_bis": "<sonne_bis>",
      "schatten_ab": "<schatten_ab>",
      "schatten_bis": "<schatten_bis>"
    },
    "name": "fassadenbeschattung_zeitfenster_ueberlappung"
  }
}

Input Schema

NameRequiredDescriptionDefault
sonne_abYesBeobachteter Start direkter Sonne auf der Glasfläche, Minuten seit Mitternacht.
sonne_bisYesBeobachtetes Ende direkter Sonne am selben Tag.
schatten_abYesBeginn der geplanten wirksamen Beschattung.
schatten_bisYesEnde der geplanten wirksamen Beschattung am selben Tag.

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 and the description only needs to add computation semantics. It does convey that this is a pure comparison of two supplied intervals producing unshaded minutes, with no external data involved, but it says nothing about boundary handling (touching intervals, zero overlap) or whether the result is a single minute count or an interval. With no output schema present, that return-value gap carries extra weight.

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 and the German clause is front-loaded, which is good. However, the trailing English sentence is essentially a translation of the first clause rather than new information, so half the text does not earn its place; the bilingual duplication also adds ambiguity about which phrasing is authoritative.

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

Completeness4/5

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

For a small pure-computation tool with four required numeric parameters, full schema coverage and no output schema, the description gives enough to call it correctly: it identifies both interval inputs and the computed quantity. It is only missing edge-case behavior and an explicit statement of the return value, which keeps it out of the top band.

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 the schema already explains each parameter as minutes since midnight. The description adds only the grouping — sun interval versus shade interval — which is modest but genuine added meaning. Baseline 3 applies since 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 concrete operation: determine the unshaded minutes ('nicht beschatteten Minuten') by comparing one observed direct-sun interval against the planned shade schedule. That is a specific verb+resource combination an agent can match to a request. It stops short of differentiating itself from similarly named sibling timing tools, but the purpose itself is unambiguous.

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?

Usage is implied rather than stated: the agent can infer the tool applies when it has exactly one observed sun interval and one planned shade window. There is no explicit when-not guidance, no note about what to do if the intervals do not overlap, and no named alternative for related facade/shade questions.

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