Skip to main content
Glama

getecoback-raumklima

dachfenster_griffzugang_ohne_krafteinwirkung

Read-only

Hält fest, ob der übliche Griff im beobachteten Aufbau ohne Umgreifen erreichbar blieb — Record access to the normal handle without reaching across a temporary seal.

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": {
      "griff_vorher": "<griff_vorher>",
      "griff_mit_kit": "<griff_mit_kit>",
      "umgreifen_noetig": "<umgreifen_noetig>"
    },
    "name": "dachfenster_griffzugang_ohne_krafteinwirkung"
  }
}

Input Schema

NameRequiredDescriptionDefault
griff_vorherYesIst der übliche Griff bei entfernten Zubehörteilen vom normalen Bedienplatz erreichbar?
griff_mit_kitYesSichtbeobachtung beim vorhandenen Zustand.
umgreifen_noetigYesWäre ein zusätzlicher Zugriff um Stoff oder Platte herum nötig?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/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. The description adds little beyond restating the subject — it does not explain what is stored or returned, how conflicting observations are treated, or what the 'beobachteter Aufbau' baseline means when griff_vorher and griff_mit_kit disagree. The word 'Hält fest' (records) creates mild ambiguity about a write, though not a clear contradiction.

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 short sentence, but the German clause and the English gloss are not parallel — the second is a noun phrase ('Record access to...') rather than a translation of 'Hält fest, ob...', which adds redundancy without adding information. The purpose statement is front-loaded, which helps.

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 required parameters, no output schema, and annotations covering safety, the definition is minimally sufficient to invoke the tool. It falls short on letting an agent predict the result or distinguish this measurement from adjacent dachfenster_* measurement tools.

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%, including an enum for griff_mit_kit, so the schema carries the parameter meaning. The description adds no additional semantics such as how umgreifen_noetig interacts with the enum value 'verdeckt' or what 'ohne Umgreifen' implies for a true/false answer. Baseline 3 is appropriate when the schema does the heavy lifting.

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 description does convey a specific subject: it captures whether the usual handle stayed reachable without reaching across in the observed setup. However, it never resolves whether the tool queries a stored observation or records a new one, and it omits the 'ohne Krafteinwirkung' (no force applied) qualifier that the tool name emphasizes, so key scope is only implied. No sibling differentiation is offered among the many dachfenster_* tools.

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 statement of when to call this tool, no prerequisite or ordering information, and no reference to alternatives such as dachfenster_kit_abnahme_vor_fensterzustand or dachfenster_oeffnung_spaltprofil_kitbereich. The agent must infer the usage context entirely from the parameter names.

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