Skip to main content
Glama

getecoback-raumklima

spuelernische_breitenprofil_messunsicherheit

Read-only

Messungen vorn, mittig und hinten mit ihrer Unsicherheit auf eine nachgewiesene Engstelle prüfen — Bound the narrowest observed opening across three measurement stations.

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": {
      "vorne_mm": "<vorne_mm>",
      "mitte_mm": "<mitte_mm>",
      "hinten_mm": "<hinten_mm>",
      "toleranz_mm": "<toleranz_mm>",
      "grenze_mm": "<grenze_mm>",
      "gleiches_hoehenband": "<gleiches_hoehenband>"
    },
    "name": "spuelernische_breitenprofil_messunsicherheit"
  }
}

Input Schema

NameRequiredDescriptionDefault
mitte_mmYesLichte Breite in der Mitte auf gleicher Höhe.
vorne_mmYesLichte Breite vorn ohne vorübergehend bewegliche Gegenstände.
grenze_mmYesDokumentierte benötigte lichte Mindestbreite am betrachteten Höhenband.
hinten_mmYesLichte Breite hinten auf gleicher Höhe.
toleranz_mmYesEigene absolute Messunsicherheit pro Station.
gleiches_hoehenbandYesWurden alle drei Stationen in derselben vorgesehenen Einbauhöhe 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 that this is a bounded check involving measurement uncertainty, but it does not explain how uncertainty is combined, what happens when gleiches_hoehenband is false, or what result is returned.

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 compact and front-loads the three station measurements plus the purpose. The English sentence largely restates the German sentence, adding some redundancy but not enough to obscure the intent.

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

Completeness2/5

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

This is a validation/calculation tool with six required parameters and no output schema, yet the description says nothing about the return value, such as whether it reports pass/fail, a margin, or the bounded narrowest width. For correct interpretation of results, that is a significant omission.

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 all six parameters are fully documented by the schema. The description maps 'vorn, mittig, hinten' to the three stations and 'Unsicherheit' to toleranz_mm at a high level, but adds no validation or format detail 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 concrete operation — checking/bounding the narrowest opening across three measurement stations — and includes the uncertainty and documented bottleneck. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools.

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 'auf eine nachgewiesene Engstelle prüfen' implies the usage situation: three station measurements, an uncertainty, and a documented minimum width are available. It does not state when not to use the tool or name an alternative such as spuelernische_lichte_hoehe_boden_arbeitsplatte_trennen.

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