Skip to main content
Glama

getecoback-raumklima

dachfenster_kit_abnahme_vor_fensterzustand

Read-only

Klärt dokumentierte Anforderungen zur Kitabnahme vor einem geplanten Wechsel der Fensterstellung — Check whether documented removal was observed before a roof-window mode 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": {
      "anleitung": "<anleitung>",
      "stoff_ab": "<stoff_ab>",
      "adapter_ab": "<adapter_ab>"
    },
    "name": "dachfenster_kit_abnahme_vor_fensterzustand"
  }
}

Input Schema

NameRequiredDescriptionDefault
stoff_abYesStoff war vor dem Wechsel vollständig abgenommen.
anleitungYesVorgabe für den konkreten Wechsel.
adapter_abYesAuslassadapter war vor dem Wechsel vollständig abgenommen.

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. The description reinforces that this is a documentation check tied to a pre-change state, but it does not describe what result is produced, how 'observed' is evaluated, or any side effects; additional disclosure is limited.

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 a single front-loaded sentence with no procedural padding. The bilingual restatement is somewhat redundant and the terminology is dense, but it remains compact.

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?

It is complete enough to understand the check's intent and preconditions, and annotations cover the safety profile. Because there is no output schema, the missing description of the return value or result shape is a notable gap for a verification tool.

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 three parameters and the enum are already documented in the schema. The description refers generally to documented requirements and removal before a window-state change but adds no parameter-specific meaning beyond the schema.

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 specific verification action ('Klär... Check whether') and the object ('dokumentierte Anforderungen zur Kitabnahme') plus timing ('vor einem geplanten Wechsel der Fensterstellung'). It is distinguishable from generic window tools, but it does not explicitly contrast with sibling checks.

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?

It supplies a temporal condition — before a planned roof-window mode change — which implies when to call it. It gives no explicit when-not guidance or named alternative tools, so the agent must infer routing.

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