Skip to main content
Glama

getecoback-climate-weather

klimafenster_plattenzuschnitt_materialbedarf

Read-only

Für mehrere gleich große abnehmbare Fensterplatten das benötigte Rohplattenformat planen — Estimate rectangular stock-sheet yield with edge and cutting allowances.

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": {
      "roh_breite_mm": "<roh_breite_mm>",
      "roh_hoehe_mm": "<roh_hoehe_mm>",
      "teil_breite_mm": "<teil_breite_mm>",
      "teil_hoehe_mm": "<teil_hoehe_mm>",
      "schnittabstand_mm": "<schnittabstand_mm>",
      "anzahl": "<anzahl>"
    },
    "name": "klimafenster_plattenzuschnitt_materialbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
anzahlYesAnzahl gleich großer rechteckiger Teile.
roh_hoehe_mmYesNutzbare Höhe der Rohplatte nach Randbeschnitt.
roh_breite_mmYesNutzbare Breite der Rohplatte nach Randbeschnitt.
teil_hoehe_mmYesFertige Höhe je rechteckigem Teil.
teil_breite_mmYesFertige Breite je rechteckigem Teil.
schnittabstand_mmYesZwischen zwei Teilen erforderliche Schnittzugabe 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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar for the description is lower. The description adds that the result is an estimate factoring in edge and cutting allowances, which is useful context, but it does not disclose what the calculation actually returns (sheet count, waste, layout) — a real gap given there is no output schema.

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?

A single sentence in two language renderings, front-loading the scenario before the calculation gloss — no wasted preamble. The bilingual duplication is mildly redundant but useful for an agent bridging German domain terms, so it is not a real defect.

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 pure-calculation tool with no output schema, the description should clarify what shape of answer to expect (e.g. how many sheets, yield ratio, leftover). It covers the inputs' intent and safety profile but leaves the return value unspecified, which is the main incompleteness.

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 six parameters (raw sheet width/height after edge trim, part width/height, cut gap, count) are already documented in the schema. The description adds essentially no parameter-level meaning beyond reinforcing 'mehrere gleich große' for the count parameter, so the baseline of 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 states a specific verb-and-resource pair: planning ('planen' / 'Estimate') a stock-sheet format ('Rohplattenformat') for multiple identically sized removable window panels. The scope restriction 'gleich große' (equal-sized) meaningfully narrows the tool's applicability. It does not, however, differentiate itself from any sibling tool by name.

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 context is implied by 'Für mehrere gleich große abnehmbare Fensterplatten', which tells the agent the scenario the tool fits. There is no explicit statement of when to use it instead of another tool, and no exclusion for mixed panel sizes beyond the implicit 'gleich große'.

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