Skip to main content
Glama

getecoback-climate-weather

waeschestaender_nutzbare_leinen_teilfreigaben

Read-only

Zwischen zwei vereinbarten Nutzungen messen, welche Leinen tatsächlich vollständig an die nächste Person übergehen — Count independently released whole lines for a second household user.

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": {
      "leinen_gesamt": "<leinen_gesamt>",
      "a_voll_belegt": "<a_voll_belegt>",
      "a_teil_belegt": "<a_teil_belegt>",
      "b_braucht_ganze_leinen": "<b_braucht_ganze_leinen>"
    },
    "name": "waeschestaender_nutzbare_leinen_teilfreigaben"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_teil_belegtYesWeitere Leinen, auf denen noch einzelne Stücke der vorherigen Person hängen.
a_voll_belegtYesDavon vollständig durch die vorherige Person belegte Leinen.
leinen_gesamtYesUnabhängig nutzbare Leinen der geprüften Aufstellung.
b_braucht_ganze_leinenYesUnabhängige vollständige Leinen, die die nächste Person benö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?

The annotations already declare a read-only, closed-world calculation, and the description does not contradict them. It adds a useful behavioral rule — only independently released whole lines are counted, so partially occupied lines do not fully transfer — but it does not disclose the calculation formula or how the needed quantity constrains the result.

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 definition is a single, compact statement with the key constraint front-loaded. It is slightly redundant because the German and English halves express the same idea, but the volume is small and no sentence is wasted.

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 four-parameter read-only calculator with no output schema, the description identifies the input context and the whole-line restriction. However, it does not state the exact computation or clearly describe the returned count, leaving some inference for an agent to call and interpret it reliably.

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 every parameter already has a German explanation. The description reinforces the central concept of fully transferring whole lines but adds little parameter-level meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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 operation — measuring/counting which whole clothes lines fully transfer from one user to a second household user. The resource is identifiable ('Leinen') and the scope ('vollständig', 'second household user') narrows the result. It does not name or distinguish a specific sibling alternative, which keeps it from a 5.

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 supplies a situational context ('Zwischen zwei vereinbarten Nutzungen' / 'for a second household user') but gives no explicit when-to-use vs when-not-to-use guidance and no alternatives. The agent must infer the use case from the scenario rather than from routing instructions.

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