Skip to main content
Glama

getecoback-raumklima

entfeuchter_testpunkte_rangwechsel

Read-only

Vergleichen, ob die Reihenfolge bei zwei geprüften Kellerbedingungen wechselt — Detect rank reversal across two verified dehumidifier test conditions.

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": {
      "a_p1": "<a_p1>",
      "b_p1": "<b_p1>",
      "a_p2": "<a_p2>",
      "b_p2": "<b_p2>",
      "punkte_bestaetigt": "<punkte_bestaetigt>"
    },
    "name": "entfeuchter_testpunkte_rangwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_p1YesEntzug A am Prüfpunkt 1 in Liter pro Tag.
a_p2YesEntzug A am Prüfpunkt 2 in Liter pro Tag.
b_p1YesEntzug B am selben Prüfpunkt 1.
b_p2YesEntzug B am selben Prüfpunkt 2.
punkte_bestaetigtYesSind jeweils Temperatur, Feuchte, Prüfablauf und Modellvarianten passend dokumentiert?

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 needn't restate it. What the description omits is the meaningful behavioral detail: what happens when punkte_bestaetigt is false (error, refusal, inconclusive verdict) and whether the operation returns a boolean flag or a richer verdict. That is a real gap for a gate-based comparison tool, but not a contradiction of 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 front-loaded sentence stating the comparison, with a bilingual mirror for clarity. It is efficient and free of hedging, though the English half largely restates the German and does not add technical content.

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 a rank-reversal check yields (a verdict, a direction, or an error when confirmation is missing); it does not. For a five-required-parameter read-only analytical tool this leaves the agent able to call it correctly but unable to anticipate the result shape.

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 each of the four numeric intake values bound to a test point and the boolean gate explained, so the schema carries the semantic burden. The description adds the framing 'rank reversal across two conditions' but no units, tolerances, or edge-case handling (e.g. equal values) beyond the schema. 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 specific operation (Vergleichen, ob die Reihenfolge wechselt = detect rank reversal) applied to a specific resource (two verified dehumidifier/Keller test conditions), so the operation is identifiable. It does not explicitly distinguish itself from any sibling, but sibling names in the catalog are largely unrelated single-purpose checks, so no conflict is apparent.

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 word "geprüften" (verified) plus the required gate parameter imply the tool is used only once both test points are documented and confirmed, and the name suggests a comparison scenario. However, the description never states when to use this instead of a plain measurement comparison, nor what to do when confirmation is absent. Usage is only implied, not prescribed.

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