Skip to main content
Glama

getecoback-raumklima

heizwaesche_hochpunkt_ruhe_nach_entnahme

Read-only

Vor und nach einer vollständigen Wäscheentnahme einen beobachteten Feuchtehöchstwert gegen dieselbe Ausgangsmessung stellen — Retain a delayed peak after all textiles have left the room.

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": {
      "randbedingungen_zwischendurch_belegt": "<randbedingungen_zwischendurch_belegt>",
      "ausgang": "<ausgang>",
      "max_vor": "<max_vor>",
      "max_nach": "<max_nach>",
      "differenz_spanne": "<differenz_spanne>"
    },
    "name": "heizwaesche_hochpunkt_ruhe_nach_entnahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
ausgangYesAbsolute Feuchte vor dem Versuch in g/m³.
max_vorYesBeobachteter Höchstwert bis unmittelbar vor Textilentnahme.
max_nachYesBeobachteter Höchstwert im zugeordneten Nachlauf nach vollständiger Entnahme.
differenz_spanneYesUnsicherheit des Vergleichs der Spitzen.
randbedingungen_zwischendurch_belegtYesBetreffen beide Höchstwerte dieselbe Zeitreihe ohne bekannte neue Feuchtequelle?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 an agent knows this is a closed, non-mutating evaluation. The description adds the relevant constraint that both peaks must belong to the same series without a known new moisture source, but says nothing about what a failed comparison yields (no output schema exists).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler, but the English half largely restates the German ('Retain a delayed peak after all textiles have left the room') rather than extending it, and its imperative phrasing reads oddly for a comparison tool. Some space is spent on redundancy instead of distinguishing information.

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?

Five required numeric/boolean inputs at full schema coverage and a clearly read-only profile make the definition callable. Still, with no output schema and no statement of what result or verdict the comparison produces, an agent cannot anticipate the return value from the description.

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 (baseline, pre-peak, post-peak, tolerance band, condition flag) is already self-documenting. The description only reinforces 'gegen dieselbe Ausgangsmessung' and adds no format, unit, or interpretation detail beyond the schema.

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 operation on a specific resource: compare an observed peak moisture value before vs. after a complete textile removal against the same baseline measurement. The domain scenario is identifiable despite dense German jargon. It does not, however, distinguish itself from the many similarly named heizwaesche sibling tools.

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 scenario ('vor und nach einer vollständigen Wäscheentnahme') implicitly conveys when the tool applies, and the required boolean encodes a same-time-series precondition. But it names no alternatives or exclusions, which matters given a sibling set full of near-synonymous peak/rest/Follow-up measurement tools.

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