Skip to main content
Glama

getecoback-climate-weather

pflege_tuchseite_beobachteter_wechselpunkt

Read-only

Bei einer erlaubten Tuchwendung die beobachtete Stückzahl pro frischer Seite ohne Übertrag ausrechnen — Estimate how many allowed fresh-face changes are needed for a grouped task.

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": {
      "seitenfolge_zulaessig": "<seitenfolge_zulaessig>",
      "abschnitte": "<abschnitte>",
      "pro_seite": "<pro_seite>",
      "pro_tuch": "<pro_tuch>",
      "tuecher": "<tuecher>"
    },
    "name": "pflege_tuchseite_beobachteter_wechselpunkt"
  }
}

Input Schema

NameRequiredDescriptionDefault
tuecherYesPassende Tücher für diese eine Gruppe im sauberen Vorrat.
pro_tuchYesUnabhängig verwendbare, belegbar frische Seiten je vorbereitetem Tuch.
pro_seiteYesBeobachtete Anzahl solcher Abschnitte bis zur eigenen definierten Seitenwechsel-Grenze.
abschnitteYesKleine gleichartige Abschnitte in der geplanten zusammenhängenden Gruppe.
seitenfolge_zulaessigYesIst die vorgesehene Nutzung frischer Seiten bei dieser Aufgabe zulässig und am Material erprobt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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 covered and the description does not contradict it. Beyond that, the description adds almost nothing: it does not say what the computation returns, how the boolean gate affects the result, or how zero/edge values behave, despite this being a pure calculator whose output is its entire value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short, but the German and English halves restate each other rather than complementing each other, so roughly half the text is redundant. Neither half is front-loaded with the concrete result being produced.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-required-parameter calculation tool with no output schema, so the description must at minimum explain the shape of the result and the role of the boolean gate. It does neither, and the domain jargon ('Tuchwendung', 'ohne Übertrag', 'Stückzahl') is left undefined, leaving the agent unable to predict the return value.

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 five parameters is already documented in the schema and the baseline is 3. The description adds no interpretation of how the parameters combine (e.g. whether pro_seite multiplies against tuecher or is capped by pro_tuch), so it does not exceed the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an operation ('ausrechnen'/estimate) and an object ('beobachtete Stückzahl pro frischer Seite'), so it is not pure tautology. However, the phrasing largely echoes the parameter names (pro_seite, pro_tuch, abschnitte) rather than stating what the tool actually computes, and it gives no basis for distinguishing this from the many other pflege_* tools.

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?

The only conditional hint is 'bei einer erlaubten Tuchwendung', which loosely maps to the seitenfolge_zulaessig gate but is not stated as a usage rule. There is no guidance on when to pick this tool over the sibling planning/sequence tools, and no mention of prerequisites or exclusions.

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