Skip to main content
Glama

getecoback-raumklima

dusche_durchflusswert_uebergabe_kopf_freigabe

Read-only

Trenne gemessene Durchflüsse von zwei protokollierten Positionen eines übernommenen Duschkopfs — Separate measured flows for two settings of a transferred showerhead

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": {
      "alt_gemessen_l": "<alt_gemessen_l>",
      "alt_messdauer_s": "<alt_messdauer_s>",
      "neu_gemessen_l": "<neu_gemessen_l>",
      "neu_messdauer_s": "<neu_messdauer_s>",
      "strahlstellung_identisch": "<strahlstellung_identisch>"
    },
    "name": "dusche_durchflusswert_uebergabe_kopf_freigabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_gemessen_lYesGesammelte Liter bei der alten dokumentierten Strahlstellung
neu_gemessen_lYesGesammelte Liter an der neuen Stelle
alt_messdauer_sYesSammelzeit für die alte Messung in Sekunden
neu_messdauer_sYesSammelzeit für die neue Messung in Sekunden
strahlstellung_identischYesStrahlstellung und Handhabung des Reglers stimmen bei beiden Messungen überein

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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. The description adds that two measurements come from a transferred showerhead and are compared, which is useful context, but it does not describe the result (flow rate? verdict?), units, or how strahlstellung_identisch influences the outcome — notable gaps for a computation 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?

A single short sentence, front-loaded with the operation and resource. The bilingual restatement adds length without new information, but overall it is lean.

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 parameters are fully documented and annotations cover the read-only nature, but the description leaves the output entirely unexplained despite there being no output schema, and it never addresses the approval/'Freigabe' semantics implied by the name. Adequate to call, incomplete to interpret.

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 a clear German description with bounds, so the schema does the heavy lifting. The tool description adds no meaning beyond it (no units of the result, no note on the boolean gate), which is the baseline expectation at this coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (measured flows of a showerhead at two logged settings) and the implied operation (separating/comparing them), but the verb is ambiguous and the tool name's 'Freigabe' (approval/release) aspect is never explained. It also gives no clue what the tool actually returns, so an agent cannot confidently distinguish it from the many sibling 'uebergabe' tools without opening the schema.

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 statement of when to use this rather than a sibling, no preconditions, and no alternatives named. The agent must infer usage entirely from the parameter list.

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