Skip to main content
Glama

getecoback-raumklima

schreibtisch_geraeteklemme_kantenabgleich

Read-only

Bemaßte Tischkante für die im Gerätehandbuch genannte Lüfterklemme prüfen — Compare two desk-edge candidates against the documented clip geometry.

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": {
      "klemme_min_mm": "<klemme_min_mm>",
      "klemme_max_mm": "<klemme_max_mm>",
      "auflage_benoetigt_mm": "<auflage_benoetigt_mm>",
      "a_dicke_mm": "<a_dicke_mm>",
      "a_auflage_mm": "<a_auflage_mm>",
      "b_dicke_mm": "<b_dicke_mm>",
      "b_auflage_mm": "<b_auflage_mm>"
    },
    "name": "schreibtisch_geraeteklemme_kantenabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_dicke_mmYesGemessene Plattenstärke an Kante A.
b_dicke_mmYesGemessene Plattenstärke an Kante B.
a_auflage_mmYesGemessene freie Auflagetiefe an Kante A.
b_auflage_mmYesGemessene freie Auflagetiefe an Kante B.
klemme_max_mmYesGrößte laut Handbuch passende Plattenstärke in mm.
klemme_min_mmYesKleinste laut Handbuch passende Plattenstärke in mm.
auflage_benoetigt_mmYesDokumentierte notwendige freie Auflagetiefe unter der Kante.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety is covered. Beyond that the description adds nothing: it does not say whether a pass/fail verdict per edge is produced, whether margins are reported, or how ties between A and B are handled — and there is no output schema to fill that gap. A read-only comparison tool still needs its result shape disclosed.

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?

Two sentences, front-loaded with the action, with no extraneous commentary. However, the second sentence is a near-verbatim English translation of the first, so roughly half the text is redundant filler rather than added information.

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 seven required numeric parameters, all fully documented, the inputs are well covered. What is missing is the outcome contract: an agent cannot tell what it receives back (verdict, per-edge fit, shortfall) and there is no output schema substitute. For a comparison tool this is a moderate but real gap.

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 every parameter carries a German description with ranges, so the schema does the heavy lifting. The description only frames the categories (measured edge values vs documented clip limits) without adding format, unit, or tolerance semantics beyond the schema. 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 names a concrete action (compare two desk-edge candidates) and a concrete reference (the documented clip geometry from the device manual), plus which physical quantities are involved. It is clearly distinct from unrelated siblings, though it never explicitly contrasts itself with a nearest alternative. The bilingual restatement adds no extra scope information.

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?

Usage is only implied: an agent can infer this is for checking whether edges A and B fit a fan clip per the manual. There is no explicit when-to-use/when-not guidance, no statement about prerequisites (e.g. manual values must be supplied by the caller), and no named alternative for related geometry checks.

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