Skip to main content
Glama

getecoback-climate-weather

textil_reparatur_bestand_neubedarf

Read-only

Nutzbaren Bestand und realistisch terminierte Instandsetzungen vor Ersatzbedarf getrennt bilanzieren — Separate confirmed serviceable stock from planned repairs before buying replacements.

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": {
      "soll": "<soll>",
      "bereit": "<bereit>",
      "reparatur_fertig": "<reparatur_fertig>",
      "pruefung_offen": "<pruefung_offen>"
    },
    "name": "textil_reparatur_bestand_neubedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
sollYesGewünschter nutzbarer Gesamtbestand.
bereitYesHeute einsatzfähige Stücke.
pruefung_offenYesZusätzliche Stücke mit ausstehendem Reparaturentscheid oder unbekanntem Fertigdatum.
reparatur_fertigYesZusätzliche Stücke, deren Reparatur bis zum Bedarfstermin zugesagt ist.

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is settled without description help. The description usefully conveys the accounting concept that repair pieces count only if realistically scheduled, but it never states what the tool actually produces (a coverage verdict, a gap figure, a breakdown) and there is no output schema to fill that gap.

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 core statement is front-loaded in a single sentence and nothing is padding. The cost is bilingual duplication, where the English half largely restates the German rather than adding information, which slightly dilutes density without harming clarity.

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?

With four required parameters at full schema coverage and read-only annotations, the input side is well covered. The remaining gap is the result: for a calculation-style tool with no output schema, the description should hint at what balance or verdict is returned, and 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 all four numeric parameters are already documented precisely in the schema, making 3 the baseline. The description's wording 'realistisch terminierte' mildly reinforces the intent behind reparatur_fertig and pruefung_offen, but adds no range, unit, or validation detail beyond what the schema states.

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 analytical operation — separating confirmed serviceable stock from repairs with committed dates before replacement purchasing — which goes well beyond the opaque compound name. An agent can grasp the domain model (usable stock vs. scheduled repairs vs. replacement need), though the verb 'bilanzieren' is nominal rather than a crisp action verb and no sibling is named for contrast.

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 'vor Ersatzbedarf' / 'before buying replacements' implies the decision point at which this tool applies, giving usable context. However, there is no explicit when-to-use vs. when-not statement, no prerequisite (e.g. that repair dates must already be confirmed), and no pointer to a contrasting tool among the many textile siblings.

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