Skip to main content
Glama

getecoback-climate-weather

textil_masshaltigkeit_vor_nach_pflege

Read-only

Gemessene Maßänderung eines Textils nach Länge und Breite getrennt dokumentieren — Record dimensional change after care in both axes.

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": {
      "gleich_trocken": "<gleich_trocken>",
      "laenge_davor": "<laenge_davor>",
      "laenge_danach": "<laenge_danach>",
      "breite_davor": "<breite_davor>",
      "breite_danach": "<breite_danach>",
      "messspanne": "<messspanne>"
    },
    "name": "textil_masshaltigkeit_vor_nach_pflege"
  }
}

Input Schema

NameRequiredDescriptionDefault
messspanneYesGeschätzte kombinierte Messspanne in cm je Vergleich.
breite_davorYesBreite vor der Pflege in cm.
laenge_davorYesLänge vor der Pflege in cm.
breite_danachYesBreite nach der Pflege in cm.
laenge_danachYesLänge nach der Pflege in cm.
gleich_trockenYesWurde im gleichen trockenen Zustand, gleicher Lage und ohne Zug gemessen?

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 covered. The description adds only that both axes are recorded separately; it says nothing about what happens to the data (computed change stored vs. returned), validation of implausible values, or how the 'gleich_trocken' quality flag affects the record. With annotations present, this is adequate but thin.

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?

Two short sentences, front-loaded with the core action and resource, with zero filler. The German/English duplication is slightly redundant but keeps the definition scannable rather than padded.

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?

There is no output schema, so the description should say what the agent gets back — e.g. the computed change per axis, sign convention, or a stored record id. Instead it stops at the input intent. For a fully-specified read-only measurement tool this is workable but leaves the result shape undefined.

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%, with every one of the six parameters individually documented including units (cm) and the measurement-span rationale. The description adds no meaning beyond the schema; naming Länge and Breite merely mirrors two existing properties. Baseline 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 concrete verb+resource: 'dokumentieren' / 'Record' of 'Maßänderung eines Textils' after care, and specifies the two axes (Länge und Breite getrennt). An agent can tell this is a dimensional-change recording tool rather than a care-cycle log. It does not explicitly separate itself from near siblings such as vorhang_pflege_nachmessung_aufhaengung or textil_pflege_nutzungszyklen_protokoll.

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 usage signal is the implicit 'nach Pflege' framing. There is no statement of when to prefer this over related textile-measurement siblings, no prerequisites (e.g. that the before/after readings must come from the same specimen and measurement span), and no 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