Skip to main content
Glama

getecoback-raumklima

heizwaesche_lueftungsphase_stabile_waage_gegenprobe

Read-only

Beim Beobachten einer Lüftungsphase Wäschegewicht und Gehalt der Raumluft getrennt lesen — Recognize air dry-down without a resolved textile mass change.

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": {
      "gekoppelte_messphase": "<gekoppelte_messphase>",
      "textil_a_g": "<textil_a_g>",
      "textil_b_g": "<textil_b_g>",
      "waage_spanne_g": "<waage_spanne_g>",
      "luft_abnahme": "<luft_abnahme>",
      "luft_spanne": "<luft_spanne>"
    },
    "name": "heizwaesche_lueftungsphase_stabile_waage_gegenprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
textil_a_gYesTextilmasse zu Beginn.
textil_b_gYesTextilmasse am Ende.
luft_spanneYesGemeinsame Unsicherheit in g/m³.
luft_abnahmeYesBeobachtete positive Abnahme der absoluten Feuchte in g/m³; bei Anstieg negativen Wert eintragen.
waage_spanne_gYesGemeinsame Unsicherheit der Textilwägungen.
gekoppelte_messphaseYesGehören Beginn und Ende der Wägung und des repräsentativen Luftmesspunkts zum selben Lüftungsfenster?

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 establish that this is a non-destructive, closed-world read/computation, so the safety burden is lifted. The description adds the interpretive behavior — that the two signals must be read separately and that the point is to detect air dry-down absent a resolvable textile mass change. It does not say how uncertainty spans are combined or what verdict shape comes back, which matters for a decision tool with no output schema.

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?

Two tight clauses, German plus a compact English gloss, with the situational trigger front-loaded before the analytical intent. No filler sentences and nothing repeated from the schema.

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 six-required-parameter comparison with uncertainty terms and a boolean coupling gate, and with no output schema, the description should convey more about the verdict logic (e.g. what happens when the coupling flag is false or when spans overlap). It does state the intended conclusion, which is the most important missing piece, but the decision boundary remains implicit.

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% and each parameter carries its own German explanation, including units (g, g/m³) and the sign convention for rising humidity. The description contributes only the framing idea of 'getrennt lesen' (keeping the two measurement families independent), which is consistent with but not additive to 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?

Names a concrete operation ('Wäschegewicht und Gehalt der Raumluft getrennt lesen') and a concrete analytical goal ('Recognize air dry-down without a resolved textile mass change'), so the agent knows this is a cross-check that separates air-borne drying from textile mass change. It does not name a sibling it displaces, so it stops short of full differentiation within the large heizwaesche_* family.

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?

'Beim Beobachten einer Lüftungsphase' scopes the situation in which to use it, which is real usage context rather than nothing. However, there is no statement of when NOT to use it, no mention of the adjacent counter-check siblings, and no prerequisites (e.g. that a coupled measurement window is required).

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