Skip to main content
Glama

getecoback-climate-weather

strommessgeraet_kostenfehler

Read-only

Euroanzeige eines Steckdosenmessgeräts nach einer falschen Preiseinstellung umrechnen. — Correct a meter cost display calculated with the wrong tariff.

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": {
      "anzeige_eur": "<anzeige_eur>",
      "eingestellt": "<eingestellt>",
      "richtig": "<richtig>"
    },
    "name": "strommessgeraet_kostenfehler"
  }
}

Input Schema

NameRequiredDescriptionDefault
richtigYesTatsächlich anzusetzender Arbeitspreis in €/kWh.
anzeige_eurYesAngezeigte Verbrauchskosten ohne zusätzliche Gebühren.
eingestelltYesIm Gerät gespeicherter Preis in €/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, offline operation. The description reinforces this by framing the task as a recalculation of a displayed figure, implying no device state is modified, but it says nothing about the return value or rounding behavior, so it adds limited context beyond the annotations.

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 action and condition front-loaded; nothing is padded. The German and English versions are near-duplicates, which is a small redundancy but serves bilingual readability.

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 simple three-parameter arithmetic correction with fully documented inputs and read-only annotations, the definition is nearly sufficient. The gap is that no output schema exists and the description never says what the tool returns (a corrected euro amount), leaving the result shape to inference.

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% — all three parameters carry units (€/kWh, €) and bounds in the schema, so the heavy lifting is already done structurally. The description's mention of a 'wrong tariff' vs a 'correct' one loosely maps to the eingestellt/richtig pair but adds no detail beyond what the schema states.

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 verb (umrechnen/correct) and a specific resource (the euro display of a plug-in energy meter), plus the trigger condition (a wrong tariff setting). The purpose is unmistakable, though it does not explicitly differentiate itself from any sibling tool — the siblings listed are unrelated household/ventilation helpers, so no confusion arises in practice.

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?

The clause 'nach einer falschen Preiseinstellung' gives a clear triggering context: use this when the meter's stored tariff differs from the true tariff. There are no explicit exclusions or named alternatives, but the scenario is narrow enough that an agent can tell when it applies.

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