Skip to main content
Glama

getecoback-climate-weather

waesche_wenden_vorderseite_rueckseite

Read-only

Eigene Kontrollen vor und nach einem Wendeschritt nach Stoffseiten aufschlüsseln — Compare observed damp points on one or both sides after turning.

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": {
      "kontrollpunkte": "<kontrollpunkte>",
      "vorher_einseitig": "<vorher_einseitig>",
      "vorher_beidseitig": "<vorher_beidseitig>",
      "nachher_einseitig": "<nachher_einseitig>",
      "nachher_beidseitig": "<nachher_beidseitig>"
    },
    "name": "waesche_wenden_vorderseite_rueckseite"
  }
}

Input Schema

NameRequiredDescriptionDefault
kontrollpunkteYesFeste Punkte, die auf beiden Stoffseiten zu beiden Zeitpunkten begutachtet wurden.
vorher_einseitigYesPunkte vor dem Wenden, die auf genau einer Seite noch feucht waren.
nachher_einseitigYesPunkte beim späteren Check mit Feuchte auf genau einer Seite.
vorher_beidseitigYesPunkte vor dem Wenden, die auf beiden Seiten noch feucht waren.
nachher_beidseitigYesPunkte beim späteren Check mit Feuchte auf beiden Seiten.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes the comparison semantics (damp points on one or both sides, before and after turning), which is real added context, but it never says what is produced—a delta, a rate, a verdict—nor whether constraints exist between the counts. Useful but incomplete beyond the annotations.

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 compact sentence with the core scenario front-loaded and no filler. The bilingual restatement is slightly redundant but aids clarity rather than padding.

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 numeric parameters, no output schema, and a computational purpose, the definition should state what the agent gets back and how the counts relate (e.g., whether the one-sided and two-sided counts must fit within kontrollpunkte). Those gaps leave the agent unable to validate inputs or interpret results fully, though the scenario itself is adequately conveyed.

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 every parameter is already documented in the schema with bounds of 0–300. The description only loosely echoes those fields ('damp points on one or both sides') and adds no formatting, relationship, or consistency guidance. Baseline 3 applies because the schema carries the parameter burden.

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 (breaking down one's own checks before and after a turning step by fabric side) plus the comparison of damp points, so the verb and resource are both identifiable. It stops short of differentiating itself from the many sibling laundry tools, and the German phrasing 'aufschlüsseln' is abstract enough that the schema is needed to confirm this is an aggregate/comparison computation rather than a lookup.

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 scenario (before/after a turning step) is implied, but there is no explicit when-to-use statement, no when-not-to-use condition, and no named alternative among the sibling tools. An agent must infer from the parameter set alone whether this is the right tool for a given laundry question.

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