Skip to main content
Glama

getecoback-climate-weather

split_klima_transportweg_masscheck

Read-only

Für ein noch verpacktes Klimagerät die geradlinige Öffnung an der engsten Stelle prüfen — Check shipping dimensions against the narrowest straight doorway in the intended orientation.

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": {
      "paket_breit_cm": "<paket_breit_cm>",
      "paket_hoch_cm": "<paket_hoch_cm>",
      "durchgang_breit_cm": "<durchgang_breit_cm>",
      "durchgang_hoch_cm": "<durchgang_hoch_cm>",
      "rangieren_erforderlich": "<rangieren_erforderlich>"
    },
    "name": "split_klima_transportweg_masscheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
paket_hoch_cmYesHöhe des Kartons in genau dieser Lage.
paket_breit_cmYesBreite des Kartons in der geplanten laut Unterlagen erlaubten Transportlage.
durchgang_hoch_cmYesLichte Höhe an derselben Stelle.
durchgang_breit_cmYesTatsächliche lichte Breite an der engsten geraden Stelle bei vollständig geöffneter Tür.
rangieren_erforderlichYesGibt es zusätzlich enge Kurven, Schwellen oder Ortswechsel in der Ausrichtung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 the safety profile is covered. The description does add one genuinely useful scoping fact – the check only covers a straight passage at the narrowest point, not curved routes or orientation changes – but it says nothing about the result (fit/no-fit, margins) or how borderline cases are reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the object and the check, then repeated in English as a gloss for clarity. No filler, no restatement of the name as prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter boolean-style clearance check with no output schema, the description supplies the scenario, the object, and the geometric scope. The remaining gap is what the tool returns, which an agent must guess, but everything needed to call it correctly is present.

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 coverage is 100%, with each parameter already carrying a precise German doc string, so the schema does the heavy lifting. The description adds only the framing that box dimensions must be taken in the intended orientation, which the schema already states. Baseline 3 applies.

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 concrete verb and resource: verify the dimensions of a still-boxed Klimagerät against the narrowest straight doorway in the planned orientation. That is specific enough to separate it from neighbour tools such as klima_abluftweg_pruefen or klima_aussenteil_stellplatz_check, though no sibling is named explicitly.

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?

Usage is only implied through the qualifier 'für ein noch verpacktes Klimagerät', which does tell the agent this applies before unboxing. There is no explicit when-not guidance and no alternative tool is pointed to, so the routing decision is left to inference.

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