Skip to main content
Glama

getecoback-raumklima

wasserverlauf_allein_doppelt_belegung

Read-only

Beobachtete Wasserentnahme von Ein- und Zweipersonentagen gegen zwei persönliche Routinen prüfen — Compare shared occupancy consumption with both observed solo routines.

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": {
      "nur_a_l_tag": "<nur_a_l_tag>",
      "nur_b_l_tag": "<nur_b_l_tag>",
      "beide_l_tag": "<beide_l_tag>",
      "einmal_gemeinsam_l_tag": "<einmal_gemeinsam_l_tag>",
      "aufgabe_gleich": "<aufgabe_gleich>"
    },
    "name": "wasserverlauf_allein_doppelt_belegung"
  }
}

Input Schema

NameRequiredDescriptionDefault
beide_l_tagYesBeobachtete Liter pro Tag mit beiden Personen.
nur_a_l_tagYesBeobachtete Liter pro Tag, an dem ausschließlich A anwesend war.
nur_b_l_tagYesBeobachtete Liter pro Tag, an dem ausschließlich B anwesend war.
aufgabe_gleichYesSind Tagesdauer, Wasserzählerumfang und erledigte Aufgaben vergleichbar?
einmal_gemeinsam_l_tagYesIn beiden Solomessungen enthaltene, bei gemeinsamer Anwesenheit jedoch nur einmal anfallende beobachtete Aufgabe in Litern.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/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. The description adds no behavioral detail beyond the purpose statement: it does not say what happens when aufgabe_gleich is false (is the comparison refused, flagged, or degraded?), nor how the 'once only when together' adjustment is applied. For a computation tool with no output schema, this leaves the result semantics opaque.

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?

It is a single sentence, which is appropriately front-loaded, but it says the same thing twice in German and English, adding length without adding information. The dash-joined bilingual duplication makes it harder to parse rather than clearer. It earns partial credit for brevity but wastes space on repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five required numeric/boolean parameters and no output schema mean the description should explain what is returned (a verdict, a delta, a ratio?) and how the shared-occupancy comparison is resolved. It explains none of this and does not state whether the tool reports a judgment or just numbers. For a non-trivial computation with no annotations covering result shape, this is a notable gap.

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, including the comparability flag aufgabe_gleich and the einmal_gemeinsam_l_tag adjustment, is already documented in the schema. The description only frames the inputs collectively as 'Ein- und Zweipersonentagen' and 'zwei persönliche Routinen' without adding units, invariants, or edge-case meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action (prüfen/compare) and a specific resource (observed water consumption on one-person and two-person days) and frames it as a comparison against two personal solo routines. An agent can tell this is a consumption-baseline check rather than a generic water tool. It stops short of 5 because the phrasing is dense bilingual jargon with no sibling differentiation.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as the wasserverlauf_erste_spuelung or verzoegerte_anlage siblings. The applicable situation (comparing solo baseline data against shared-occupancy readings) is only implied by the field names in the schema. Nothing tells the agent what prerequisite data is required beyond the parameters themselves.

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