Skip to main content
Glama

getecoback-raumklima

klimafenster_schliessbeleg_nach_kitabnahme

Read-only

Hält Schließstellung und sichtbare Griffstellung nach vollständiger Kitabnahme getrennt fest — Record sash closure and normal handle position separately after kit removal.

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": {
      "kit_status": "<kit_status>",
      "fluegel": "<fluegel>",
      "griff": "<griff>"
    },
    "name": "klimafenster_schliessbeleg_nach_kitabnahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
griffYesBeobachteter Griffzustand.
fluegelYesBeobachtete Endstellung des Flügels.
kit_statusYesStatus der temporären Teile.

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, so the safety profile is covered, and the description adds the meaningful context that this happens only after complete kit removal. However, the verb 'festhalten/record' sits in slight tension with a read-only hint and the description does nothing to resolve whether anything is persisted or returned. With annotations carrying the safety burden, a 3 is appropriate.

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 content is front-loaded and short, but it is stated twice (German then an English restatement) with essentially identical wording, which doubles length without adding information. No sentence is wasted in the German original, but the bilingual duplication is pure redundancy.

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 simple three-enum, fully documented, read-only recording tool with no output schema, the definition covers the essentials and the annotations cover safety. It is nonetheless thin: it does not indicate how the recorded pair of positions is used downstream or how it relates to adjacent kit-removal/comparison tools, leaving the agent to infer the workflow context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with documented enums for all three parameters, so the baseline is 3. The description adds a small but real nuance by specifying 'sichtbare Griffstellung' (the visible handle position), clarifying that griff is an observation of what is seen rather than an inferred state. It does not mention kit_status, but the schema already documents it fully.

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 concrete recording action plus two distinct resources (Schließstellung / Griffstellung) and stresses that they are captured 'getrennt' (separately), which tells an agent this is a two-fact observation record rather than a single merged state. It never names a sibling tool or a contrasting operation, so differentiation from the surrounding klimafenster family is left implicit.

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 phrase 'nach vollständiger Kitabnahme' supplies a real precondition for when the tool applies, which is more than nothing. There is no when-not guidance, no mention of what to do when kit parts remain, and no routing to neighbouring tools, so usage is only implied.

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