Skip to main content
Glama

getecoback-raumklima

geraete_label_rundung_abstand

Read-only

Feststellen, ob die bekannte Anzeigerundung eine kleine Differenz zwischen vergleichbaren Verbrauchswerten erklären kann — Check whether report rounding alone could explain a small difference between two comparable labels.

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_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "schritt_a_kwh": "<schritt_a_kwh>",
      "schritt_b_kwh": "<schritt_b_kwh>",
      "basis_gleich": "<basis_gleich>"
    },
    "name": "geraete_label_rundung_abstand"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesAbgelesener Energiekennwert A auf der gleichen Bezugsbasis.
b_kwhYesAbgelesener Energiekennwert B.
basis_gleichYesGleiche Prüfbasis und Rundung auf den jeweils nächsten Schritt belegt?
schritt_a_kwhYesBelegte Rundungsstufe für A in kWh.
schritt_b_kwhYesBelegte Rundungsstufe für B in kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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, consistent with a pure analytical check. The description adds the key behavioral idea of isolating rounding as the sole explanation, but it does not describe the result shape or any assumptions beyond the input schema.

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

Conciseness5/5

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

The definition is a single, front-loaded sentence with no wasted wording. The bilingual German/English phrasing is compact and preserves the same clear meaning.

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

Completeness4/5

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

Given full schema coverage, safe read-only annotations, and no output schema, the description is nearly complete: it states the check and implies a yes/no determination. It could be stronger by clarifying the return format or edge-case limitations.

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 five parameters are already documented in the schema. The description adds only the high-level notion of comparable labels and rounding, without extra parameter semantics.

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 states a specific analytical check: whether report rounding alone can explain a small difference between comparable consumption values. It is clear what the tool determines, but it does not explicitly differentiate itself from the many sibling label/comparison tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage context: use it when checking whether rounding alone could account for a small difference between comparable labels. It does not name exclusions or alternatives, so it falls short of full when/when-not guidance.

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