Skip to main content
Glama

getecoback-raumklima

dachfenster_auslass_sichtgrenze_von_innen

Read-only

Dokumentiert, welche Teile eines Dachfensterauslasses ohne Hinauslehnen überhaupt überprüfbar waren — Record which roof-window outlet sections were visible from indoors.

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": {
      "ende": "<ende>",
      "adapter": "<adapter>",
      "stoff": "<stoff>"
    },
    "name": "dachfenster_auslass_sichtgrenze_von_innen"
  }
}

Input Schema

NameRequiredDescriptionDefault
endeYesAuslassende vom sicheren Innenstandort.
stoffYesStoff unmittelbar am Adapter.
adapterYesVerbindung am Auslassadapter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 usefully adds the constraint that assessment happens from a safe indoor position without leaning out — behaviourally meaningful for how the values should be judged. It does not say whether the record is persisted, returned, or what happens to prior entries, and the verb 'Dokumentiert' sits in mild tension with a read-only annotation, though not enough to count as a contradiction.

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?

One sentence, front-loaded with the recording verb and scoped to the resource. The German/English duplication is slightly redundant but serves as a disambiguation aid for an opaque tool name, and there is no filler beyond that.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, three-enum documentation tool with no output schema and fully described parameters, the description supplies the essential missing frame: what is being recorded and under which physical constraint. Only the fate of the recorded assessment and the meaning of 'sichtbar_auffaellig' versus 'nicht_sichtbar' as decision criteria are left unstated.

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% and all three enum parameters (ende, stoff, adapter) are individually documented in the schema, so the description does not need to carry parameter detail. The description only implies that multiple 'Teile' are judged visible or not; it adds no mapping between the enum values and the physical conditions, so baseline 3 applies.

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 gives a concrete verb plus object ('Record' / 'Dokumentiert') and a specific scope ('which roof-window outlet sections were visible from indoors'), which an agent can separate from the surrounding non-roof-window siblings. It stops short of naming the outlet-/adapter-specific siblings it overlaps with, so the agent must infer differentiation from the scope noun alone.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The only contextual cue is the embedded safety condition ('without leaning out'), which implies when this observation applies but never states prerequisites, exclusions, or what to do if a section is not visible.

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