Skip to main content
Glama

getecoback-climate-weather

strommessung_hochrechnen

Read-only

Steckdosenmessung auf Nutzungstage hochrechnen — Project meter readings across representative days.

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": {
      "kwh": "<kwh>",
      "hours": "<hours>",
      "days": "<days>",
      "price": "<price>"
    },
    "name": "strommessung_hochrechnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwhYesGemessene Energie in kWh.
daysYesVergleichbare Betriebstage.
hoursYesMessdauer in Stunden.
priceYesEigener Strompreis in EUR/kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 agent knows this is a safe, closed-world computation, and the description does not contradict that. Beyond that, the description discloses nothing behavioural: not whether the result is energy, cost, or both, despite a 'price' parameter hinting at cost output. For a pure calculation this is acceptable but thin.

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?

Two short sentences, front-loaded with the action, with a parallel English gloss. No filler and nothing redundant.

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?

With no output schema and four required numeric inputs, the description should at minimum convey what comes back; it implies a projection onto usage days but never states whether the return is kWh, cost, or a per-day figure. Everything else an agent needs to invoke it correctly is covered by the fully documented schema and the read-only annotation.

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 all four parameters are required with units and ranges documented in the schema (kWh, hours, days, price in EUR/kWh). The description adds no meaning beyond that and does not clarify how price interacts with the extrapolated result. Baseline 3 is appropriate when the schema carries the parameter burden.

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 gives a specific verb-plus-resource: 'hochrechnen' (extrapolate) applied to 'Steckdosenmessung' / 'meter readings', i.e. scaling a plug-meter measurement to representative usage days. An agent can tell this is the extrapolation tool rather than a raw measurement tool like its siblings. It stops short of naming how it differs from adjacent calculation siblings (e.g. geraetetakt_aus_messung, geraetewechsel_rechnen).

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?

The usage scenario is only implied: you have a plug-meter reading and want to project it onto usage days. There is no explicit when-to-use, no prerequisites, and no statement of which sibling to pick instead for a related calculation. An agent can infer the context but must do the work itself.

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