Skip to main content
Glama

getecoback-raumklima

gebraucht_behaelter_sitz_linke_rechte_auflage

Read-only

Bei sichtbarer Abweichung zweier gleichartiger Auflagen Messspiel und Beobachtung trennen — Compare visible seated-container alignment against your measurement tolerance.

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": {
      "gleichartige_auflagen": "<gleichartige_auflagen>",
      "links_mm": "<links_mm>",
      "rechts_mm": "<rechts_mm>",
      "messspanne_mm": "<messspanne_mm>",
      "sitz_auffaellig": "<sitz_auffaellig>"
    },
    "name": "gebraucht_behaelter_sitz_linke_rechte_auflage"
  }
}

Input Schema

NameRequiredDescriptionDefault
links_mmYesBeobachteter Spalt links in mm.
rechts_mmYesBeobachteter Spalt rechts in mm.
messspanne_mmYesSelbst ermittelte gemeinsame Unsicherheit in mm.
sitz_auffaelligYesIst der ohne Eingriff beobachtete Sitz zusätzlich auffällig?
gleichartige_auflagenYesSind beide Messpunkte laut Unterlagen im selben Sollzustand vergleichbar und ohne Eingriff zugänglich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 only adds the cryptic directive "Messspiel und Beobachtung trennen" without explaining what the tool computes, what it returns, or how it behaves when gleichartige_auflagen is false. The instruction is open to interpretation rather than operational.

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 short clauses, so nothing is padded, but the structure is not front-loaded: the reader gets a conditional preamble before the actual action. The bilingual phrasing and the dash-joined second clause read as compressed notes rather than a deliberate definition.

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?

The tool takes five required inputs with no output schema, so the description is the only place a result could be characterized — and it says nothing about what comes back or how the tolerance comparison resolves. For a decision-style tool with an all-required schema, that gap matters.

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 five parameters are self-documenting. The description only alludes to "measurement tolerance", which loosely maps to messspanne_mm, and adds no format, unit, or interpretation guidance beyond the schema. Baseline 3 applies where the schema does the heavy lifting.

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 description names a concrete comparison ("Compare visible seated-container alignment against your measurement tolerance") which maps to the tool name's left/right support subject. However, the German preamble and the compressed English clause make it hard to state plainly what the tool produces or decides. It communicates a domain area more than a specific verb+outcome.

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?

"Bei sichtbarer Abweichung zweier gleichartiger Auflagen" gives an implicit trigger condition: use it when two comparable supports show a visible deviation. No alternatives or exclusions are named, and there is no statement about what to do when the supports are not comparable.

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