Skip to main content
Glama

getecoback-climate-weather

spueler_lieferweg_wendeflaeche_aufmass_schablone

Read-only

Eine komplett beobachtete einfache Lieferschablone am Wendepunkt gegen eine veränderte Zustellhülle prüfen — Decide whether an earlier swept-corner proof still applies.

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": {
      "holzprobe_a_mm": "<holzprobe_a_mm>",
      "holzprobe_b_mm": "<holzprobe_b_mm>",
      "neu_a_mm": "<neu_a_mm>",
      "neu_b_mm": "<neu_b_mm>",
      "haltung_und_aufmass_gleich": "<haltung_und_aufmass_gleich>",
      "gesamte_kurve_belegt": "<gesamte_kurve_belegt>"
    },
    "name": "spueler_lieferweg_wendeflaeche_aufmass_schablone"
  }
}

Input Schema

NameRequiredDescriptionDefault
neu_a_mmYesAbmessung der vom Lieferdienst vorgesehenen Hülle in Richtung A.
neu_b_mmYesEntsprechende Abmessung in Richtung B.
holzprobe_a_mmYesGrößte in Richtung A erfasste Abmessung der damaligen vollständigen Schablone.
holzprobe_b_mmYesEntsprechende Abmessung in Richtung B.
gesamte_kurve_belegtYesWar die ganze Bewegung der maßgetreuen einfachen Schablone sichtbar und frei?
haltung_und_aufmass_gleichYesGleicher Wendepunkt, gleiche Höhe, gleiche Orientierung und keine weiteren vorstehenden Teile?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered and the description does not need to restate them. The description adds the framing that this is a comparison between an old and a new geometry rather than a standalone measurement, but it says nothing about outcome semantics (what a 'no' answer implies) or result form. With annotations carrying the safety profile, this is adequate but thin.

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 core condition is front-loaded and the whole description is two short clauses. The German and English sentences largely restate the same idea, which is mild redundancy, but the length is far from bloated and the decision framing lands immediately.

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?

For a six-parameter, fully required, fully documented read-only decision tool with no output schema, the description covers the input-side question but not the return. An agent knows what to supply but not what the answer looks like or how to interpret a negative verdict. Adequate, with a clear remaining gap on outcome.

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 one of the six parameters has an explicit German description, including the two booleans about full curve visibility and identical turning point/height/orientation. The description adds no additional meaning about ranges, units, or how the numeric pairs are compared. Baseline 3 applies since the schema does the work.

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 specific verb and object pair: checking a previously fully observed simple delivery template ('Lieferschablone am Wendepunkt') against a changed delivery envelope ('veränderte Zustellhülle'), reinforced by the English 'Decide whether an earlier swept-corner proof still applies'. An agent can tell this is a re-validation/decision tool rather than a fresh measurement. It stops short of naming any sibling it contrasts with, so it is clear but not differentiating.

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?

'Decide whether an earlier swept-corner proof still applies' implies the triggering situation (an existing proof plus a changed envelope), which is real usage context. However, there is no explicit when-not condition, no mention of what to do if the proof does not apply, and no reference to alternative siblings for a first-time measurement. Guidance is implied rather than stated.

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