Skip to main content
Glama

getecoback-climate-weather

textil_ersatzbezug_pflegepassung

Read-only

Maße des trockenen vorhandenen Bezugs mit Maßtoleranz und Pflegevorgaben eines Ersatzbezugs abgleichen — Check a replacement cover’s documented dimensions and care fit.

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": {
      "passform_bestaetigt": "<passform_bestaetigt>",
      "pflegeweg_bestaetigt": "<pflegeweg_bestaetigt>",
      "alt_laenge": "<alt_laenge>",
      "alt_breite": "<alt_breite>",
      "neu_laenge": "<neu_laenge>",
      "neu_breite": "<neu_breite>",
      "passend_bis": "<passend_bis>"
    },
    "name": "textil_ersatzbezug_pflegepassung"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_breiteYesTrockene relevante Bezugsbreite.
alt_laengeYesTrockene relevante Bezugslänge.
neu_breiteYesAuf derselben Variante dokumentierte Breite.
neu_laengeYesAuf der genauen Ersatzvariante dokumentierte Länge.
passend_bisYesFür beide Maße akzeptierte Abweichung, nach realer Aufnahme ermittelt.
passform_bestaetigtYesSind Verschluss, Befestigung und Schnitt für den vorgesehenen Gegenstand bestätigt?
pflegeweg_bestaetigtYesIst der dokumentierte Pflegeweg mit dem verfügbaren Ablauf vereinbar?

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, and 'abgleichen' is consistent with a pure read-only comparison. Beyond that the description adds the tolerance and care-compatibility dimensions of the check but not what a verdict looks like or whether the two boolean confirmations gate the outcome.

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?

A single tight sentence that front-loads the comparison object and the tolerance/care scope, with a parallel English rendering. The bilingual duplication is slightly redundant for a German-named tool but adds no bloat.

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 seven-parameter, all-required comparison tool with no output schema, the description covers the inputs' purpose but leaves the decision logic opaque — notably how 'passend_bis' interacts with the two boolean confirmations and what the tool returns. Adequate to call correctly, not complete enough to predict the result.

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 seven parameters are already documented in the schema, including the tolerance field and both confirmation booleans. The description echoes the tolerance and care concepts but adds no syntax, units, or decision rule beyond what the schema provides, so 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?

States a specific verb and resource: compare ('abgleichen') the dry existing cover's dimensions against a replacement cover's documented dimensions and care requirements, with an explicit tolerance notion. A reader can tell it is a fit-check tool, though it does not differentiate itself from nearby textile comparison siblings.

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?

Usage is only implied by the wording — you call it when verifying whether a replacement cover is dimensionally and care-path compatible. There is no explicit when-to-use, no prerequisites (measured dry, on the exact variant), and no statement of what to do instead when the check fails.

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