Skip to main content
Glama

getecoback-climate-weather

fenster_freigabe_nach_stellungswechsel

Read-only

Prüfen, welche freiwilligen Fensterfreigaben nach einem bestätigten Umbau noch zum aktuellen Zustand gehören — Detect which shared window permissions predate a configuration change.

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": {
      "a_bestaetigt_min": "<a_bestaetigt_min>",
      "b_bestaetigt_min": "<b_bestaetigt_min>",
      "zuletzt_geaendert_min": "<zuletzt_geaendert_min>",
      "beide_freigaben_noetig": "<beide_freigaben_noetig>"
    },
    "name": "fenster_freigabe_nach_stellungswechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_bestaetigt_minYesLetzte Bestätigung der Person A für den geprüften Zustand.
b_bestaetigt_minYesLetzte Bestätigung der Person B auf derselben Zeitachse.
zuletzt_geaendert_minYesZeitpunkt der jüngsten relevanten Änderung der geplanten Fensterstellung.
beide_freigaben_noetigYesDie Beteiligten haben für diese konkrete Nutzung beide Zustimmungen vereinbart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 by structured data. The description contributes the precondition that the configuration change must be confirmed and that the check is scoped to 'current state'. It says nothing about what is returned (a set of stale permissions? a boolean?) or how ties/edge cases are resolved, which matters because no output schema exists.

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 front-loaded with the German purpose statement, which is good. The appended English sentence is a near-literal restatement that adds no new information, so part of the text does not earn its place.

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?

This is a four-required-parameter comparison tool with no output schema, so the description should explain what the check yields and how the result should be read. It provides no return-value information at all, leaving the agent unable to know whether it receives a filtered list, a boolean, or per-person verdicts. For a decision tool of this shape, that is a material 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 four parameters (two confirmation timestamps, last-change timestamp, and the mutual-consent flag) are already documented in the schema. The description adds no interpretation of how these timestamps are compared or what role 'beide_freigaben_noetig' plays in the decision. Baseline 3 applies when the schema carries the load.

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 German sentence names a specific verb ('Prüfen') and object ('freiwillige Fensterfreigaben nach einem bestätigten Umbau'), so the general intent is discernible. However, the domain jargon ('Fensterfreigabe', 'Umbau', 'Zustand') is never grounded, and nothing distinguishes this from closely named siblings such as 'fensterschutz_saisonwechsel_freigabe_zwei_raeume' or 'klima_fenster_nachtbetrieb_check'. The English gloss merely restates the German rather than sharpening the purpose.

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?

The phrase 'nach einem bestätigten Umbau' implies a triggering condition, which is a small amount of context. But there is no statement of when to prefer this tool over the many sibling 'freigabe' tools, no exclusion criteria, and no prerequisites such as needing a confirmed change first. An agent must guess its place in the catalog.

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