Skip to main content
Glama

getecoback-climate-weather

textil_pflege_nutzungszyklen_protokoll

Read-only

Zwei vergleichbare Textilien anhand protokollierter Nutzungen und festgehaltener Ausfälle nachbeobachten — Compare recorded wear outcomes per use without projecting lifespan.

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": {
      "einsatz_gleich": "<einsatz_gleich>",
      "a_nutzungen": "<a_nutzungen>",
      "a_beobachtungen": "<a_beobachtungen>",
      "b_nutzungen": "<b_nutzungen>",
      "b_beobachtungen": "<b_beobachtungen>"
    },
    "name": "textil_pflege_nutzungszyklen_protokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_nutzungenYesProtokollierte Nutzungen in Stoffgruppe A.
b_nutzungenYesProtokollierte Nutzungen in Stoffgruppe B.
einsatz_gleichYesWaren Einsatzart, Pflege und Kriterien zum Aussortieren bei beiden Gruppen gleich?
a_beobachtungenYesNutzungen mit jeweils einem beobachteten Reparatur- oder Aussortiergrund in A.
b_beobachtungenYesNutzungen mit jeweils einem beobachteten Reparatur- oder Aussortiergrund in B.

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 safety is covered and the description need not restate it. What it does add is the semantic constraint that only observed wear outcomes are reported and no lifespan projection is made, plus the implicit precondition that the two textiles must be comparable. It stops short of saying what the comparison produces or how non-comparable groups are handled.

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?

One compact sentence plus an English gloss; the core action is front-loaded and the non-projection constraint lands last as a qualifier. The bilingual duplication costs a little space but aids comprehension rather than adding noise.

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 five required, fully documented parameters and read-only annotations, an agent has enough structured information to invoke the tool. What remains unclear is the nature of the result — whether it yields a comparison verdict, a rate, or a divergence — and there is no output schema to fill that gap, so the description could say more about the returned comparison.

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 five parameters (use counts, observation counts, and the equality flag) are already documented in German at the field level. The description restates the concepts at a high level without adding format, unit, or edge-case meaning beyond the schema, so the baseline of 3 applies.

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 specific operation on a specific resource: comparing two comparable textiles based on logged use counts and recorded failures ('protokollierter Nutzungen und festgehaltener Ausfälle'), and explicitly excludes extrapolation ('without projecting lifespan'). It is clear enough to distinguish from a generic measurement tool, but it never contrasts itself with any of the similarly named textile siblings, leaving that differentiation to the caller.

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 'without projecting lifespan' implies a boundary — this tool reports observed outcomes, not forecasts — which is a useful implicit when-not. However, there is no explicit statement of when to choose this over the other textile protocol tools, and no mention of prerequisites such as the two groups needing identical use type, care and sorting criteria.

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