Skip to main content
Glama

getecoback-climate-weather

heissluft_schublade_einsaetze_auflageflaechen

Read-only

Bei zwei zugelassenen Einsätzen die wirklich nutzbare Bodenfläche getrennt von der belegten Randzone vergleichen — Compare the observed usable tray surface of two compatible inserts.

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": {
      "boden_cm2": "<boden_cm2>",
      "rand_a_cm2": "<rand_a_cm2>",
      "rand_b_cm2": "<rand_b_cm2>",
      "benoetigt_cm2": "<benoetigt_cm2>",
      "formen_geprueft": "<formen_geprueft>"
    },
    "name": "heissluft_schublade_einsaetze_auflageflaechen"
  }
}

Input Schema

NameRequiredDescriptionDefault
boden_cm2YesTatsächlich vermessene ebene Bodenfläche des Garraums in cm².
rand_a_cm2YesDavon belegte oder laut Anleitung freizuhaltende Teilfläche bei Einsatz A.
rand_b_cm2YesDavon entsprechende Teilfläche bei Einsatz B.
benoetigt_cm2YesVorab für die kalte Passprobe begründete nötige zusammenhängende Fläche.
formen_geprueftYesBeide verbleibenden Flächen wurden in der benötigten Form und Aufstellung geprüft.

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 the safety profile is covered. The description adds the conceptual split between usable floor and occupied edge zone, but does not say what the comparison yields or that the tool is a pure derivation with no side effects and no external lookup.

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?

It is a single sentence, front-loaded with the core distinction, and the English gloss aids comprehension. The bilingual duplication is slightly redundant but not wasteful for a non-obvious domain term.

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?

There is no output schema, so the description should hint at what comes back (a difference, a verdict on which insert leaves more usable area). It describes the comparison inputs well but leaves the result shape entirely unspecified for a pure computation 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 coverage is 100% with all five required parameters individually documented in German, so the schema carries parameter meaning. The description only reiterates the usable-floor-versus-edge-zone framing and adds no format, unit, or constraint detail beyond what the schema states.

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 (compare) and a specific resource (the usable tray floor area of two inserts), and it distinguishes usable floor from the occupied edge zone, which frames what is being compared. It stops short of naming how it differs from siblings such as heissluft_mitnutzung_einzelschublade_kompromiss, so an agent must infer the boundary.

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?

The precondition 'bei zwei zugelassenen Einsätzen' implies the situation in which to use it (two approved inserts, comparing usable surface). There is no explicit when-not guidance, no mention of what to use instead when only one insert is relevant, and no prerequisites 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