Skip to main content
Glama

getecoback-climate-weather

waeschestaender_leinen_reichweite

Read-only

Nutzbare Leinen für die bevorzugte Arbeitshöhe summieren — Count drying lines inside a self-measured preferred height range.

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": {
      "hoehe_a_cm": "<hoehe_a_cm>",
      "anzahl_a": "<anzahl_a>",
      "hoehe_b_cm": "<hoehe_b_cm>",
      "anzahl_b": "<anzahl_b>",
      "unten_cm": "<unten_cm>",
      "oben_cm": "<oben_cm>"
    },
    "name": "waeschestaender_leinen_reichweite"
  }
}

Input Schema

NameRequiredDescriptionDefault
oben_cmYesSelbst gewählte obere Grenze für häufige Handgriffe.
anzahl_aYesAnzahl Leinen in der ersten Ebene.
anzahl_bYesAnzahl Leinen in der zweiten Ebene.
unten_cmYesSelbst gewählte untere Grenze für häufige Handgriffe.
hoehe_a_cmYesHöhe der Leinen in der ersten Ebene.
hoehe_b_cmYesHöhe der Leinen in der zweiten Ebene.

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 already declare readOnlyHint=true and openWorldHint=false, so the safety profile is carried by structured data. The description adds that the height window is self-measured, which is genuinely useful context, but it says nothing about what the result looks like (a bare count), nor how lines exactly on the unten/oben boundary are treated. With annotations present, this is adequate but not rich.

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 German statement followed by an English gloss. Slightly redundant for a bilingual reader, but it wastes no words and puts the constraint ahead of everything else.

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, fully required computation with no output schema, an agent knows what to pass but not exactly what comes back or how boundary cases resolve. The definition is serviceable but leaves the result contract and edge-case behavior to inference.

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%, with each of the six required parameters described in the schema itself, so the baseline is 3. The description does not add the one thing the schema lacks: the relationship between hoehe_a_cm/hoehe_b_cm and unten_cm/oben_cm, i.e. whether bounds are inclusive and whether a level with zero matching lines is skipped. It confirms range semantics only in general terms.

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?

States a specific verb and resource: summing usable drying lines ('Nutzbare Leinen ... summieren') restricted to a self-chosen working-height window. The English gloss reinforces the same idea. It does not explicitly distinguish itself from the sibling waeschestaender_stellflaeche, which is a footprint tool, so the boundary is left implicit.

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?

'bevorzugte Arbeitshöhe' hints at the scenario, but there is no explicit when-to-use, no when-not-to-use, and no named alternative among the many sibling tools. An agent must guess that this is the counting tool rather than the footprint or clearance tool.

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