Skip to main content
Glama

getecoback-raumklima

steckdosenleiste_schalter_zugriffsweg

Read-only

Bei einer vorgesehenen schaltbaren Leiste freie Strecke zum vorhandenen Schalter prüfen — Check obstruction-free physical access to an existing switched power strip.

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": {
      "freier_weg_cm": "<freier_weg_cm>",
      "probe_bedarf_cm": "<probe_bedarf_cm>",
      "schalter_sichtbar": "<schalter_sichtbar>"
    },
    "name": "steckdosenleiste_schalter_zugriffsweg"
  }
}

Input Schema

NameRequiredDescriptionDefault
freier_weg_cmYesAm vorgesehenen Ort gemessene freie Breite im Zugang zum Schalter.
probe_bedarf_cmYesIn einer trockenen Probe gemessene Breite für den eigenen Handzugriff.
schalter_sichtbarYesDer vorhandene Schalter ist aus der vorgesehenen Zugriffsposition sichtbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-open-world check. The description adds useful behavioral context by framing the operation as an obstruction-free physical access check using measured clearance and a dry-run hand-access probe.

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 wasted setup. The German and English versions duplicate the same content, which is mildly redundant but still efficient and clear.

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 read-only check with fully documented required parameters and safety annotations, the purpose is adequately covered. However, there is no output schema, and the description does not say what the check returns or how pass/fail is determined, leaving a meaningful gap for invocation.

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 the schema itself explains each measurement in detail. The description only broadly frames the parameters as part of checking the free access path, adding little 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 states a specific verb, 'prüfen/check', and a specific resource, 'freie Strecke zum vorhandenen Schalter' on a planned switchable power strip. It is clear what the tool does, but it does not explicitly distinguish itself from any sibling tool.

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 'Bei einer vorgesehenen schaltbaren Leiste' implies the planning context in which this check applies. However, it gives no explicit when-not guidance, prerequisites, or alternatives, so the agent must infer usage boundaries.

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