Skip to main content
Glama

getecoback-climate-weather

strombilanz_restverbrauch

Read-only

Erkennen, wie viel Verbrauch noch keinem einzeln gemessenen Gerät zugeordnet ist. — Reconcile a total meter reading with disjoint appliance measurements.

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": {
      "haushalt_kwh": "<haushalt_kwh>",
      "zugeordnet_kwh": "<zugeordnet_kwh>"
    },
    "name": "strombilanz_restverbrauch"
  }
}

Input Schema

NameRequiredDescriptionDefault
haushalt_kwhYesVerbrauch laut Gesamtzähler im betrachteten Zeitraum.
zugeordnet_kwhYesSumme der einzeln gemessenen Geräte im selben Zeitraum ohne Doppelzählung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the read-only, closed-world profile, so the description only needed to add calculation behavior. It does not explain what happens when zugeordnet_kwh exceeds haushalt_kwh (negative residual), how rounding works, or whether any validation beyond the schema bounds is applied.

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 short sentences, front-loaded with the purpose. The German and English sentences are near-duplicates, which costs a little, but neither is padded or vague.

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?

The tool is simple (two numeric inputs) but there is no output schema, so the description must explain what is returned — a residual kWh figure, possibly negative — and it does not. Combined with the absent usage guidance, an agent cannot fully predict the call's result.

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 coverage is 100% and both parameters carry their own German descriptions, so the schema does the heavy lifting. The description adds the reconciliation framing ('disjoint', 'without double counting' via 'ohne Doppelzählung' in the schema) but no new syntax or format detail.

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 states the resource ('Verbrauch', 'total meter reading', 'appliance measurements') and the intent ('Reconcile'), but the core operation is only implied: nowhere does it say it computes the difference between total and assigned consumption. An agent must infer from the parameter names that the result is the residual.

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 tool versus any sibling, no preconditions, and no note on which situations are unsuitable. The only implicit cue is the word 'Reconcile', which does not route the agent against other energy-balance tools in the catalog.

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