Skip to main content
Glama

getecoback-climate-weather

waeschenetz_liegeplaetze_mit_abstand

Read-only

Gleich große, liegend zu trocknende Stücke auf einer nutzbaren Rechteckfläche anordnen — Compare two aligned flat-drying layouts with measured clearance.

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": {
      "lage_bestaetigt": "<lage_bestaetigt>",
      "flaeche_a": "<flaeche_a>",
      "flaeche_b": "<flaeche_b>",
      "textil_a": "<textil_a>",
      "textil_b": "<textil_b>",
      "abstand": "<abstand>"
    },
    "name": "waeschenetz_liegeplaetze_mit_abstand"
  }
}

Input Schema

NameRequiredDescriptionDefault
abstandYesEingeplanter Abstand zwischen Stücken in cm.
textil_aYesLänge eines ausgelegten Stücks in cm.
textil_bYesBreite eines ausgelegten Stücks in cm.
flaeche_aYesFreie Auflagelänge in cm.
flaeche_bYesFreie Auflagebreite in cm.
lage_bestaetigtYesSind liegendes Trocknen und die Auflage für diese Textilien bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds that the comparison uses measured clearance between equal-sized pieces, but it does not disclose what the comparison returns or how the two layouts are evaluated. With annotations covering read-only behavior, this is moderately transparent but incomplete for a calculation 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?

The description is a single compact sentence that front-loads the action and resource. The bilingual phrasing creates slight redundancy but remains efficient and easy to scan.

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 read-only calculation with no output schema, the description covers the input context but not the expected result. An agent knows what the tool compares, yet must infer what output it produces and how the comparison is presented.

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%, and the schema documents each of the six required parameters in German. The description mentions equal-sized pieces, a rectangular area, and clearance, which loosely maps to the parameters, but adds no syntax, constraints, or interpretation beyond the schema.

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 concrete action (compare two aligned flat-drying layouts with measured clearance) and the subject matter (equal-sized pieces on a usable rectangular area). It is specific enough to distinguish this as a layout-comparison calculation rather than a generic laundry tool, though the German/English phrasing is slightly mixed.

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?

It implies the tool is for comparing two flat-drying layouts, but gives no explicit when-to-use instruction, prerequisites, or when-not-to-use guidance. No alternative tool is named, so the agent must infer the appropriate context.

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