Skip to main content
Glama

getecoback-raumklima

heizwaesche_langsamere_zone_rangwechsel_im_verlauf

Read-only

Erkennen, ob die anfangs feuchtere Gruppe später nicht mehr den Trocknungsendpunkt bestimmt — Detect a rank reversal between unchanged placement groups within one drying run.

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": {
      "bezug_und_platz_fest": "<bezug_und_platz_fest>",
      "a_frueh": "<a_frueh>",
      "b_frueh": "<b_frueh>",
      "a_spaet": "<a_spaet>",
      "b_spaet": "<b_spaet>",
      "differenzspanne": "<differenzspanne>"
    },
    "name": "heizwaesche_langsamere_zone_rangwechsel_im_verlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_fruehYesFrüher Restwasserwert A in g je 100 g eigener trockener Masse.
a_spaetYesSpäterer Restwasserwert A in denselben Einheiten.
b_fruehYesEntsprechender früher Wert B.
b_spaetYesEntsprechender späterer Wert B.
differenzspanneYesKombinierte Unsicherheit für den Unterschied je Zeitpunkt.
bezug_und_platz_festYesWurden beide Stoffgruppen an ihren Positionen belassen und Restwerte auf einen vergleichbaren Trockenbezug normiert?

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 covered and the description does not contradict it. It adds the interpretive framing of what constitutes a reversal (wetter group no longer setting the endpoint), but says nothing about what the tool returns or how near-threshold cases are treated.

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 front-loaded sentence pair with the purpose stated first and no filler. The German/English duplication is slightly redundant but each half is compact and the English clause aids disambiguation.

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?

Six required numeric/boolean parameters with no output schema means the description should ideally explain the shape of the verdict (e.g. reversal yes/no or a margin against differenzspanne). That return-side context is missing, though the input side is fully covered by the schema.

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 units, ranges and per-field meaning, so the schema carries the parameter burden. The description contributes only indirectly, by explaining that A/B are placement groups and that the comparison concerns the initially wetter one; baseline 3 is appropriate.

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 detection task — whether the initially wetter group later stops determining the drying endpoint, i.e. a rank reversal between unchanged placement groups within one run. Verb and resource are both present and specific. It does not, however, distinguish itself from siblings with similar names such as entfeuchter_testpunkte_rangwechsel or vergleichstest_gewichtung_rangwechsel.

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 phrasing 'innerhalb eines Trocknungslaufs' and 'unveränderter Platzierung' implies the applicable scenario, and the schema's bezug_und_platz_fest encodes a precondition. But there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for a different reversal 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