Skip to main content
Glama

getecoback-climate-weather

thermo_vorhang_packungsbreite_abdeckung

Read-only

Rechne aus Artikelmaß und Stückzahl die Stoffabdeckung eines Vorhangsets — Calculate curtain coverage from the listed size and pack quantity

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": {
      "etikettbreite_cm": "<etikettbreite_cm>",
      "etikett_bezug": "<etikett_bezug>",
      "schals_im_set": "<schals_im_set>",
      "zielbreite_cm": "<zielbreite_cm>",
      "stofffaktor": "<stofffaktor>"
    },
    "name": "thermo_vorhang_packungsbreite_abdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
stofffaktorYesGewählte Stoffbreite je cm wirksamer Breite einschließlich gewünschter Falten
etikett_bezugYesWorauf bezieht sich die aufgedruckte Breite?
schals_im_setYesAnzahl Schals laut Packung
zielbreite_cmYesZu bedeckende Breite einschließlich selbst geplanter seitlicher Zugaben
etikettbreite_cmYesAufgedruckte Breite

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 without prose. The description adds that the result is derived from label size and pack quantity, but it does not say what the output looks like (a coverage figure, a comparison against zielbreite_cm, a shortfall) or how the etikett_bezug ambiguity is resolved, which is the real behavioral question for this tool.

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

Conciseness3/5

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

The single sentence is front-loaded and free of filler, but the German text is immediately repeated in English, which doubles the length without adding information. Efficient in content, mildly redundant in form.

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 pure five-parameter calculator with full schema coverage, the description covers the core intent, but with no output schema it should state what is returned and how it relates to the target width. That gap leaves an agent unsure whether the result is a boolean adequacy check or a numeric coverage value.

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 five parameters, including the etikett_bezug enum and the stofffaktor range, are already documented in the schema. The description only echoes two of them (size, quantity) and adds no interpretation such as how stofffaktor interacts with zielbreite_cm, so the 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 gives a specific verb plus resource ('Rechne aus ... die Stoffabdeckung eines Vorhangsets') and names the two input classes (Artikelmaß, Stückzahl), so an agent knows this is a coverage calculation for a curtain set. It does not distinguish itself from the sibling vorhang_parkbreite_fensterweg, which also deals with curtain geometry, so it stops short of a 5.

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?

There is no statement of when to use this tool versus the neighbouring curtain/coverage tools, and no prerequisites or exclusions. The only usage signal is the implied 'you have a label size and a pack quantity', which the schema already conveys.

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