Skip to main content
Glama

getecoback-climate-weather

wohnungsstrom_stromspiegel

Read-only

Jahresverbrauch einer Wohnung mit passender Haushaltsgröße nach Stromspiegel einordnen. — Benchmark apartment electricity against the cited German household averages.

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": {
      "personen": "<personen>",
      "jahresverbrauch_kwh": "<jahresverbrauch_kwh>",
      "warmwasser_elektrisch": "<warmwasser_elektrisch>"
    },
    "name": "wohnungsstrom_stromspiegel"
  }
}

Input Schema

NameRequiredDescriptionDefault
personenYesPersonen im Haushalt als Auswahl. Nur Wohnungen.
jahresverbrauch_kwhYesBezug in kWh aus einer vollständigen Jahresabrechnung.
warmwasser_elektrischYesWird das Warmwasser elektrisch bereitet? Bei ja sind diese Referenzwerte nicht anwendbar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the useful provenance note that benchmarks are 'cited German household averages', which tells the agent results are reference-based rather than computed. It does not say what the classification looks like (bands/thresholds) or how non-applicable inputs are reported.

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 with the operation front-loaded; the German/English duplication is redundant but arguably serves bilingual agents and costs little. No filler or hedging.

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?

With no output schema, the description should convey what the 'Einordnung' returns (consumption bands, labels, comparison to average) and how the warm-water exclusion manifests; it does neither. It is adequate for the inputs but incomplete on results for a benchmark-style tool.

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%, so all three parameters are already documented, including enum options and the warm-water caveat. The description only reinforces the household-size mapping ('passender Haushaltsgröße') and apartment-only scope, adding little beyond the schema.

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 concrete operation ('Jahresverbrauch ... einordnen' / 'Benchmark') on a concrete resource (apartment annual electricity consumption against Stromspiegel household averages), so an agent knows exactly what it does. It implicitly distinguishes apartments from houses, but names no sibling tool, so differentiation is only partial.

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; the only exclusion ('Bei ja sind diese Referenzwerte nicht anwendbar') lives in the schema's warmwasser_elektrisch field, not in the description. The use case is inferable from the verb 'einordnen', but alternatives and prerequisites are left to the agent.

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