Skip to main content
Glama

getecoback-climate-weather

thermovorhang_bahnenbedarf

Read-only

Mit Wunschüberstand und Kräuselmaß die Anzahl gleich großer Vorhangbahnen bestimmen — Calculate curtain panels from measured coverage and the chosen fullness.

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": {
      "oeffnung_cm": "<oeffnung_cm>",
      "ueberstand_links_cm": "<ueberstand_links_cm>",
      "ueberstand_rechts_cm": "<ueberstand_rechts_cm>",
      "stofffaktor": "<stofffaktor>",
      "bahn_flach_cm": "<bahn_flach_cm>"
    },
    "name": "thermovorhang_bahnenbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
oeffnung_cmYesZu bedeckende Breite der gemessenen Öffnung.
stofffaktorYesVerhältnis flache Stoffbreite zu fertiger Breite entlang der Schiene.
bahn_flach_cmYesFlache Stoffbreite einer verwendbaren Bahn in cm.
ueberstand_links_cmYesGewollte Überdeckung links, in der Aufhängung verfügbar.
ueberstand_rechts_cmYesGewollte Überdeckung rechts, in der Aufhängung verfügbar.

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 agent knows this is a side-effect-free, closed-domain calculation. The description is consistent with that but adds little beyond it — notably it does not say how the panel count is rounded (up vs. nearest) or how remainder fabric is treated, which are the behavioral details that matter for a computation tool.

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 sentences, front-loaded with the German statement of purpose and the key inputs. The bilingual duplication (German sentence immediately restated in English) is slightly redundant but does not obscure the message.

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 five-parameter, fully-required calculation with no output schema, the description covers the inputs and the general result ('number of equal-sized panels'). It is incomplete on output semantics — rounding rule, whether the count is an integer, and what happens with the residual width — which an agent would need to trust the result.

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%, so every parameter (oeffnung_cm, ueberstand_links_cm, ueberstand_rechts_cm, stofffaktor, bahn_flach_cm) is already documented in the schema. The description reinforces the concepts of desired overhang and fullness ratio but adds no units, ranges, or interpretation beyond what the schema provides, 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 states a specific verb ('bestimmen'/'Calculate') and a specific resource ('Anzahl gleich großer Vorhangbahnen'/'curtain panels'), plus the inputs that drive the result (coverage, fullness). It is immediately clear what the tool computes, though it does not differentiate itself against any sibling.

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: the mention of 'measured coverage and the chosen fullness' signals this is a sewing/curtain-planning calculation. There is no explicit when-to-use statement, no prerequisites, and no guidance on alternatives or edge cases (e.g., what to do when the opening is already covered).

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