Skip to main content
Glama

getecoback-climate-weather

spueler_lieferkarton_aufrecht_zwei_tuerprofile

Read-only

Zwei gerade Durchgänge anhand der bestätigten aufrechten Lieferhülle aufmessen — Identify straight delivery openings with insufficient width or height.

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": {
      "huelle_b_mm": "<huelle_b_mm>",
      "huelle_h_mm": "<huelle_h_mm>",
      "a_b_mm": "<a_b_mm>",
      "a_h_mm": "<a_h_mm>",
      "b_b_mm": "<b_b_mm>",
      "b_h_mm": "<b_h_mm>",
      "huelle_und_transport_bestaetigt": "<huelle_und_transport_bestaetigt>"
    },
    "name": "spueler_lieferkarton_aufrecht_zwei_tuerprofile"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_b_mmYesKleinste lichte Breite Durchgang A.
a_h_mmYesKleinste lichte Höhe A.
b_b_mmYesKleinste lichte Breite Durchgang B.
b_h_mmYesKleinste lichte Höhe B.
huelle_b_mmYesBreite der tatsächlich angebotenen aufrechten Lieferhülle inklusive Tragehilfen.
huelle_h_mmYesHöhe derselben Hülle im vorgesehenen Lieferzustand.
huelle_und_transport_bestaetigtYesLieferzustand und aufrechte Ausrichtung vom Lieferdienst bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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, consistent with a pure measurement/check operation. The description adds little beyond that: it repeats the reliance on a confirmed upright delivery hull (already a required parameter) and never says whether the result is a pass/fail verdict, per-opening numbers, or both. No output schema exists, so that gap matters.

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?

Two short clauses with no padding, and the measuring action is front-loaded. The cost is a mismatched bilingual pairing where the English sentence does not translate the German one, which is waste rather than length.

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?

Seven required parameters with no output schema and no annotation coverage beyond read-only mean the description had to explain what comes back and how the hull is compared against each opening. It explains neither, leaving the agent unable to predict the response for a moderately parameterized tool.

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 seven parameters are already documented in the schema, and the description adds no syntax, units, or relationships between the hull dimensions and the two doorway dimensions. Baseline 3 applies when the schema carries the full burden.

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 German clause names a concrete action ("aufmessen") on a concrete object ("zwei gerade Durchgänge") anchored to the delivery hull, but the English gloss shifts the purpose to "identify ... insufficient width or height," so the agent gets two partially different framings of one tool. It does not distinguish this tool from the many sibling measurement 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?

No statement of when to use this over alternatives, no prerequisites, no exclusions. The only implied condition is that the delivery state is confirmed, which is already encoded as a required boolean parameter rather than guidance in the description.

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