Skip to main content
Glama

getecoback-raumklima

dachfenster_sonnenschutz_schaltstellungen_abgleichen

Read-only

Prüft beobachtete Kombinationen aus Dachfensterschutz und Abluftstellung für zwei unterschiedliche Nutzungsziele — Distinguish tested shade positions for light control and exhaust operation.

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": {
      "lichtziel": "<lichtziel>",
      "beim_kuehlen": "<beim_kuehlen>",
      "gleichzeitig_beobachtet": "<gleichzeitig_beobachtet>"
    },
    "name": "dachfenster_sonnenschutz_schaltstellungen_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
lichtzielYesFür das eigene Lichtziel tatsächlich genutzte Position.
beim_kuehlenYesBeobachtete Position während des dokumentierten Kühlaufbaus.
gleichzeitig_beobachtetYesBeide Funktionen waren in derselben Position gleichzeitig sichtbar nutzbar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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, and 'Prüft' is consistent with that read-only profile, so there is no contradiction. The description adds the domain scope (two distinct usage goals being compared) but says nothing about what the check yields or how a mismatch is reported, which matters since there is no output schema.

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 a single front-loaded sentence, which is good, but the German-to-English bilingual restatement is redundant and the English half is an awkward translation that adds no information. Half the text could be removed with no loss.

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?

With three fully documented parameters and read-only annotations, the definition is adequate for invoking the tool, but it omits what the 'Prüfung' returns and what constitutes a match or mismatch, which is the agent's main open question for a comparison tool with no output schema.

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%, with enums and per-parameter descriptions for lichtziel, beim_kuehlen, and gleichzeitig_beobachtet, so the baseline is 3. The phrase 'zwei unterschiedliche Nutzungsziele' loosely maps to the two position parameters but adds no format or interpretation detail beyond the schema.

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 clause states a specific action ('Prüft beobachtete Kombinationen aus Dachfensterschutz und Abluftstellung') on a recognizable resource, but the trailing English fragment ('Distinguish tested shade positions for light control and exhaust operation') is a loose gloss rather than a precise restatement. It never distinguishes this from the many sibling '*_abgleichen' tools, so the agent must infer which comparison it performs.

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 description implies the tool is for checking observed shade/exhaust combinations against two usage goals, but gives no explicit when-to-use condition, no exclusions, and no named alternative among the numerous sibling reconcile tools. Selection between this and e.g. dachfenster_hitzeschutz_typabgleich is left entirely 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