Skip to main content
Glama

getecoback-raumklima

wasserjournal_liter_aufloesung

Read-only

Kleine Volumendifferenzen zwischen Wasserzählern mit gleichem Messumfang mit ihrer Rundungsauflösung einordnen — Bound a water-volume difference using separate display increments.

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_liter": "<a_liter>",
      "b_liter": "<b_liter>",
      "a_schritt_liter": "<a_schritt_liter>",
      "b_schritt_liter": "<b_schritt_liter>"
    },
    "name": "wasserjournal_liter_aufloesung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_literYesVolumen A aus zwei auf nächste Anzeigestufe gerundeten Ablesungen, in Litern.
b_literYesVolumen B im gleichen Fenster und mit gleichem Leitungsumfang, in Litern.
a_schritt_literYesAnzeigeschritt pro Ablesung für A in Litern.
b_schritt_literYesAnzeigeschritt pro Ablesung für B in Litern.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the pure-computation, side-effect-free nature is covered structurally. The description adds that the operation accounts for rounding resolution when judging a difference, but says nothing about what the result expresses (e.g. whether the difference is within resolution) and there is no output schema to fill that gap.

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?

Very short and front-loaded: the core constraint (small difference, same measurement scope, rounding resolution) appears first. The German/English duplication is slightly redundant but serves as a bilingual gloss rather than padding.

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 four-parameter, all-required computation tool with no output schema, the description should indicate what the returned verdict looks like (bound, interval, or classification). It conveys the input relationship but leaves the result semantics unstated, so an agent knows when to call it but not fully what it receives.

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 all four parameters are documented, including units (liters) and bounds. The description contributes the key relational constraint that the two volumes share the same measurement scope while having separate display increments, which slightly clarifies the pairing of a/b parameters. That is a modest addition over the schema, matching the baseline 3.

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 (einordnen/bound) on a specific resource (Volumendifferenzen zwischen Wasserzählern) and qualifies the inputs as rounded readings with display increments. An agent can tell this is a tolerance/bounding computation rather than a raw difference or a lookup. It stops short of explicitly naming a sibling it differs from, but the resource is distinctive enough.

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?

Usage is only implied: 'Kleine Volumendifferenzen' and 'mit gleichem Messumfang' signal the intended scenario (small differences between meters of the same measurement scope), but there is no explicit when-to-use/when-not guidance and no named alternative for computing a plain difference or a statistical comparison.

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