Skip to main content
Glama

getecoback-raumklima

kueche_teigformen_passprobe_getrennte_innenmasse

Read-only

An einer vorhandenen kalten Form zwischen nominellem Volumen und geprüftem Einsetzen eines Zubehörs unterscheiden — Check a cold insert against usable internal form dimensions.

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": {
      "gemessen_tiefe_cm": "<gemessen_tiefe_cm>",
      "gemessen_breite_cm": "<gemessen_breite_cm>",
      "einsatz_tiefe_cm": "<einsatz_tiefe_cm>",
      "einsatz_breite_cm": "<einsatz_breite_cm>",
      "geprueftes_spiel_cm": "<geprueftes_spiel_cm>"
    },
    "name": "kueche_teigformen_passprobe_getrennte_innenmasse"
  }
}

Input Schema

NameRequiredDescriptionDefault
einsatz_tiefe_cmYesMaximale äußere Tiefe des Zubehörs in dieser Stellung.
einsatz_breite_cmYesMaximale äußere Breite des Zubehörs in dieser Stellung.
gemessen_tiefe_cmYesKleinste vorgesehene nutzbare Tiefe der Form in cm, an der eingesetzten Höhe.
gemessen_breite_cmYesKleinste entsprechende Innenbreite in cm.
geprueftes_spiel_cmYesDokumentierter seitlicher Abstand pro Seite in cm für diese Probe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations cover only readOnlyHint=true and openWorldHint=false, so safety is settled, but the description adds little beyond restating the check. It does not say what verdict is produced (fit/no-fit, margins, pass/fail), how geprueftes_spiel_cm changes the outcome, or what tolerance logic is applied — and there is no output schema to fall back on.

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 definition is short, but it is a bilingual duplication where the German half is convoluted and mentions a concept (nominal volume) absent from the tool's inputs. Front-loading is acceptable, yet the ambiguity costs more than the brevity saves.

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?

For a five-required-parameter computation tool with no output schema, the description should explain the decision rule and expected return. It does neither, leaving the agent unable to predict what the invocation will produce beyond a vague 'check'.

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 is already documented in German at the field level. The description reinforces that the check uses usable internal dimensions versus insert outer dimensions, but contributes no additional semantics such as units handling or how the measured-versus-insert values interact.

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 English clause "Check a cold insert against usable internal form dimensions" names a concrete comparison between an insert and a form's internal dimensions. However, the German preamble talks about distinguishing from "nominellem Volumen," a factor that appears nowhere in the schema (no volume parameter), leaving the actual objective ambiguous. It also offers no differentiation from the many sibling kueche_* 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 this check should be run, what prerequisites apply (e.g. that the form is already cold and measured), or what alternative tool to use instead. The agent must infer all routing from the name alone.

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