Skip to main content
Glama

getecoback-raumklima

waeschestaender_fluegellast_drei_textilien

Read-only

Drei gewogene Textilien auf zwei Flügel innerhalb der ausdrücklich dokumentierten Teilgrenzen verteilen — Find a measured two-wing load split for three textiles.

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": {
      "traglasten_bestaetigt": "<traglasten_bestaetigt>",
      "links_max_g": "<links_max_g>",
      "rechts_max_g": "<rechts_max_g>",
      "gesamt_max_g": "<gesamt_max_g>",
      "stueck_a_g": "<stueck_a_g>",
      "stueck_b_g": "<stueck_b_g>",
      "stueck_c_g": "<stueck_c_g>"
    },
    "name": "waeschestaender_fluegellast_drei_textilien"
  }
}

Input Schema

NameRequiredDescriptionDefault
stueck_a_gYesMasse des feuchten Stücks A.
stueck_b_gYesMasse des feuchten Stücks B.
stueck_c_gYesMasse des feuchten Stücks C.
links_max_gYesDokumentierte erlaubte Zusatzlast am linken Flügel.
gesamt_max_gYesDokumentierte erlaubte gesamte Zusatzlast für den vorgesehenen Aufbau.
rechts_max_gYesDokumentierte erlaubte Zusatzlast am rechten Flügel.
traglasten_bestaetigtYesSind für das genaue Modell eine Gesamtgrenze, getrennte Flügelgrenzen und die betrachtete Aufstellung dokumentiert?

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 establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that the computation is bounded by documented limits, but for a solver-style tool it never says what happens when no feasible split exists (error, refusal, approximate result) — a notable behavioral gap beyond what annotations tell the agent.

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 front-loaded sentence with the operative constraint stated first, plus a bilingual restatement that aids comprehension at minor redundancy cost. No filler or hedging language.

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?

Seven required parameters, no output schema, and a computational result whose form (per-wing assignment, totals, feasibility verdict) is never described. For a read-only solver with no output schema, the description should at least sketch what comes back; it does not.

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 each of the seven parameters is already explained in German. The description adds only a conceptual mapping — three weighed pieces onto two wings under documented partial limits — without clarifying units, tolerance, or the meaning of the confirmation boolean. Baseline 3 is appropriate when the schema carries the semantics.

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 names a specific operation — distributing three weighed textiles across two wings under documented partial limits — which is a concrete verb+resource statement rather than a restatement of the tool name. It falls short of 5 because it never distinguishes itself from the nearby waeschestaender_* siblings (Leinenreichweite, Haube, Stellfläche), leaving the agent to infer which rack question this answers.

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 'innerhalb der ausdrücklich dokumentierten Teilgrenzen' implies a precondition (documented per-wing and total limits must exist), which loosely maps to the traglasten_bestaetigt flag. However, there is no explicit when-to-use/when-not-to-use instruction and no named alternative for cases where limits are undocumented.

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