Skip to main content
Glama

getecoback-raumklima

sonnenschutz_geteiltes_fenster_minutenquote

Read-only

Einen einmaligen Wechsel zwischen zwei vereinbarten Stellungen im selben Zeitfenster auf beide Mindestzeiten prüfen — Allocate one shared shade window without denying either agreed minimum.

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": {
      "fenster_min": "<fenster_min>",
      "taglicht_minimum_min": "<taglicht_minimum_min>",
      "schatten_minimum_min": "<schatten_minimum_min>",
      "stellwechsel_min": "<stellwechsel_min>"
    },
    "name": "sonnenschutz_geteiltes_fenster_minutenquote"
  }
}

Input Schema

NameRequiredDescriptionDefault
fenster_minYesZeit, in der beide vereinbarten Stellungen geplant werden sollen.
stellwechsel_minYesGemessene Zeit des einen erlaubten Wechsels.
schatten_minimum_minYesVereinbarte Mindestzeit in der geprüften beschattenden Stellung.
taglicht_minimum_minYesVereinbarte Mindestzeit zur Tageslichtnutzung.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds useful behavioral context by stating that only one change is allowed and that both agreed minimums must be preserved, but it does not explain the result format or what happens when the check fails.

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 definition is compact and front-loads the core operation before the English allocation summary. The bilingual phrasing is slightly redundant, but every sentence contributes to understanding and there is no unnecessary detail.

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?

For a four-parameter read-only check with no output schema, the description covers the essential purpose and constraint but omits what a successful or failed check returns. Given the fully documented schema and annotations, this is adequate but not fully complete.

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 four parameters are already documented in the input schema. The description reinforces the notion of two agreed positions and two minimum durations but adds no syntax, units, or constraints beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific action ('prüfen') and resource: checking a single permitted change between two agreed positions within one shared time window against both minimum durations. This is clear enough for an agent to understand the core operation, though it does not explicitly differentiate itself from similarly named shading or window siblings.

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 usage context is implied by the allocation scenario ('Allocate one shared shade window without denying either agreed minimum'), but there is no explicit guidance on when to choose this tool versus alternatives or when not to use it. It is adequate but leaves routing decisions to inference.

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