Skip to main content
Glama

getecoback-climate-weather

waescheleine_klammern_versetzte_stuecke

Read-only

Zuerst breit ausgehängte Stücke und dann schmale Stücke mit Leinen- und Klammerbudget einplanen — Allocate two textile widths on one unobstructed clothesline.

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": {
      "leine_cm": "<leine_cm>",
      "abstand_cm": "<abstand_cm>",
      "breit_cm": "<breit_cm>",
      "schmal_cm": "<schmal_cm>",
      "breite_stuecke": "<breite_stuecke>",
      "schmale_stuecke": "<schmale_stuecke>",
      "klammern": "<klammern>"
    },
    "name": "waescheleine_klammern_versetzte_stuecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
breit_cmYesGehängte Breite eines breiten Stücks.
klammernYesVerfügbare Klammern. Werkzeug rechnet mit zwei pro Stück.
leine_cmYesFreie zusammenhängende Leinenlänge.
schmal_cmYesGehängte Breite eines schmalen Stücks.
abstand_cmYesAbstand zwischen benachbarten Stücken.
breite_stueckeYesAnzahl breiter priorisierter Stücke.
schmale_stueckeYesAnzahl schmaler Stücke.

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 safety is covered. The description adds the genuinely useful behavioral rule that wide pieces are allocated with priority before narrow ones under a shared line-and-peg budget, but it says nothing about what happens when the budget is exhausted (partial allocation vs. error) or what the computation returns.

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 compact sentence with the ordering rule front-loaded, so an agent gets the key logic immediately. The German and English halves largely duplicate each other, which costs some tokens without adding new information.

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 seven-required-parameter planning tool with no output schema, the description conveys the input concept but never describes the result (how many pieces fit, leftover line/peg budget, or failure behavior). The absence of any return-value hint is the main gap given that no output schema exists.

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 including the peg cost of two per piece is already documented in the schema. The description contributes the priority semantics (breit before schmal) and the framing of leine_cm and klammern as shared budgets, but it omits abstand_cm spacing entirely, leaving one required parameter's role to the schema alone.

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 concrete verb (einplanen/allocate) and resource (two textile widths on one unobstructed clothesline), plus the allocation order (wide pieces first, then narrow). It is specific enough to distinguish a capacity-allocation task, though it does not name or contrast any sibling tool.

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 phrase 'Zuerst breit ausgehängte Stücke und dann schmale Stücke' encodes the intended planning sequence, which is real usage guidance for the caller. However, there is no statement of when this tool should be chosen over related clothesline tools, nor any prerequisites or exclusion conditions.

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