Skip to main content
Glama

getecoback-climate-weather

werkstatt_probestueck_passbereich_streuung

Read-only

Die Spannweite mehrerer bereits vermessener ungefährlicher Probestücke mit einem gewählten Passbereich abgleichen — Compare variation of organizer prototypes with user-measured target bounds.

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": {
      "untergrenze_mm": "<untergrenze_mm>",
      "obergrenze_mm": "<obergrenze_mm>",
      "kleinstes_mm": "<kleinstes_mm>",
      "groesstes_mm": "<groesstes_mm>",
      "stuecke": "<stuecke>"
    },
    "name": "werkstatt_probestueck_passbereich_streuung"
  }
}

Input Schema

NameRequiredDescriptionDefault
stueckeYesAnzahl einzeln vermessener Probestücke.
groesstes_mmYesGrößter Messwert der Probestücke in mm.
kleinstes_mmYesKleinster Messwert der Probestücke in mm.
obergrenze_mmYesObere selbst festgelegte Zielabmessung in mm.
untergrenze_mmYesUntere selbst festgelegte Zielabmessung in mm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish read-only and non-open-world behavior, and the description adds that this is a comparison of pre-measured samples against user-chosen bounds. It does not explain the result of the comparison, failure conditions, or any assumptions about the measurements.

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 comparison purpose in one German sentence, followed by an English gloss. The bilingual repetition is mildly redundant but not wasteful enough to impair selection.

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?

All required inputs are fully described by the schema, but there is no output schema and the description does not explain what the comparison returns or how a mismatch should be interpreted. For a five-parameter analytical tool, that leaves a meaningful 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%, so all five parameters are already documented. The description usefully groups three parameters as the measured sample spread and two as the chosen target bounds, but it adds little detail beyond that relational framing.

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 gives a specific verb/resource: comparing the spread of already measured sample pieces against a chosen target tolerance range. The bilingual gloss reinforces the German statement, though it does not explicitly distinguish this tool from similarly named dispersion 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?

It implies the right context: samples are already measured and the user has selected lower/upper target bounds. However, it does not state when to choose this tool over alternatives such as other scatter or tolerance comparisons.

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