Skip to main content
Glama

getecoback-raumklima

fensterschutz_saisonwechsel_freigabe_zwei_raeume

Read-only

Zwei Räume beim Wechsel von abnehmbarem Fensterschutz nach Aufbewahrung und Fensterbedienung sortieren — Prepare a reversible shade change only where storage and operation are ready.

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_fenster_bedienbar": "<a_fenster_bedienbar>",
      "b_fenster_bedienbar": "<b_fenster_bedienbar>",
      "a_altschutz_untergebracht": "<a_altschutz_untergebracht>",
      "b_altschutz_untergebracht": "<b_altschutz_untergebracht>",
      "beides_rueckbaubar": "<beides_rueckbaubar>"
    },
    "name": "fensterschutz_saisonwechsel_freigabe_zwei_raeume"
  }
}

Input Schema

NameRequiredDescriptionDefault
beides_rueckbaubarYesWurde der geplante Rückbau für diese konkrete Miet- oder Wohnsituation geklärt?
a_fenster_bedienbarYesIst der übliche Fensterweg mit dem geplanten Behang im ersten Raum bestätigt?
b_fenster_bedienbarYesFensterweg im zweiten Raum bestätigt?
a_altschutz_untergebrachtYesKann der entfernte Zustand des ersten Raums trocken und zugeordnet untergebracht werden?
b_altschutz_untergebrachtYesIst die Aufbewahrung für den zweiten Raum vorbereitet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 supplied structurally. The description adds the decision rule ('only where storage and operation are ready') and frames the change as reversible, which is useful context. It does not contradict the read-only annotation, but it also never clarifies whether a failed check blocks the change or what the agent should do next — a notable gap that 'Prepare' hints at but never resolves.

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?

Two short sentences with no padding, and the German statement is front-loaded before the English gloss. The structure is efficient; the only cost is that brevity here shades into under-specification rather than 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?

This is a five-required-parameter gate tool with no output schema, so the description should explain what the boolean combination produces and what the agent receives back. Instead it stops at the precondition, leaving the outcome of the release check — and the consequence of a false value — entirely undocumented. For a decision tool of this shape, that is a significant completeness 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%: each of the five required booleans carries its own German question (window operability per room, old protection stored per room, reversibility clarified). The description adds only the aggregate idea of 'storage and operation', so it neither duplicates nor meaningfully enriches the per-parameter semantics. Baseline 3 applies when the schema does the heavy lifting.

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 a resource (two-room removable window protection, seasonal change) and an intent ('sortieren' / prepare a reversible change), so the topic is identifiable. However, it never states what the tool actually does operationally — whether it evaluates the five readiness booleans and returns a release decision, or performs an action. The odd verb 'sortieren' and the vague 'freigabe' framing leave the agent guessing, and no sibling (e.g. fenster_freigabe_nach_stellungswechsel, fensterbehang_winter_lichtgewinn_zwei_bloecke) is distinguished.

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 clause 'only where storage and operation are ready' implies the precondition for invoking the tool, which is a form of usage guidance. But there is no explicit when-to-use/when-not statement, no mention of prerequisites such as confirming both rooms first, and no routing to an alternative sibling for single-room or non-seasonal cases.

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