Skip to main content
Glama

getecoback-raumklima

schubladeneinsatz_aushebehoehe

Read-only

Herausheben eines losen Schubladeneinsatzes bei geöffneter Schublade prüfen — Check the measured vertical removal space before adding a removable drawer organizer.

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": {
      "lift_benoetigt_cm": "<lift_benoetigt_cm>",
      "lift_frei_cm": "<lift_frei_cm>",
      "zugang_dokumentiert": "<zugang_dokumentiert>"
    },
    "name": "schubladeneinsatz_aushebehoehe"
  }
}

Input Schema

NameRequiredDescriptionDefault
lift_frei_cmYesVertikal freier Raum über dem Einsatz bei vorgesehener Öffnungsstellung.
lift_benoetigt_cmYesHöhe, um den geplanten Einsatz senkrecht über seine Führung oder Schubladenkante zu heben.
zugang_dokumentiertYesSenkrechter Weg wurde bis zum höchsten Hindernis am tatsächlichen Ort gemessen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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. The description adds the framing that this is a pre-installation verification against an actual on-site measurement, but says nothing about what verdict or result the check produces, which is the main behavioral unknown.

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 German statement is front-loaded and efficient, but it is immediately duplicated in English, roughly doubling the text without adding information. Nothing is padded beyond that bilingual repetition.

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 three-parameter read-only check with a fully described schema, the description covers what is being checked and when. Because there is no output schema, it should at least indicate what the check returns (a pass/fail clearance verdict), and that is missing.

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%, so every parameter (required lift space, available free space, documented access) is already fully documented in the schema. The description adds no units, ranges, or interpretation rules beyond that, so the baseline of 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 pairs a specific verb (checking) with a specific resource (the vertical removal space for a loose drawer insert in an opened drawer), which is far more informative than the cryptic German name alone. It does not name any sibling alternative, but the sibling catalog is topically unrelated, so the differentiation requirement is largely moot.

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?

'before adding a removable drawer organizer' gives a clear moment-of-use cue, which is real guidance. There are no when-not conditions and no named alternatives, so the usage framing stops short of full routing advice.

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