Skip to main content
Glama

getecoback-raumklima

fensterrahmen_entwaesserung_dokumentieren

Read-only

Eine beobachtete Öffnung im Fensterrahmen vor dem Abdichten richtig einordnen — Decide what to document when a window-frame opening might be drainage.

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": {
      "oeffnung": "<oeffnung>",
      "sichtbar_verdeckt": "<sichtbar_verdeckt>",
      "wasser_im_rahmen": "<wasser_im_rahmen>"
    },
    "name": "fensterrahmen_entwaesserung_dokumentieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
oeffnungYesFunktion laut Unterlagen des Fensters.
wasser_im_rahmenYesSteht nach Regen sichtbar Wasser im betroffenen Rahmenabschnitt?
sichtbar_verdecktYesIst die Öffnung bereits ganz oder teilweise verdeckt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds workflow context ('before sealing') and frames the tool as an assessment/documentation decision, but it does not describe the result or what gets recorded.

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?

A single compact sentence, front-loading the scenario and the decision. The bilingual restatement is slightly redundant but not wasteful.

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 low-complexity, three-parameter documentation aid, the definition gives the workflow context and the schema fully documents inputs. However, with no output schema, it still leaves unclear what the tool returns or how the classification translates into documentation.

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 coverage is 100%; all three parameters, including the enum values, are documented in the schema. The description adds no parameter-specific meaning beyond that, so the baseline score of 3 is appropriate.

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 task and resource: classifying an observed opening in a window frame before sealing when it might be drainage. It is clear enough to distinguish the tool's domain, though it does not explain the documentation action beyond 'decide what to document.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear usage context: before sealing, when a window-frame opening might be drainage. It does not state when not to use it or compare against any alternative, so it stops short of full routing guidance.

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