Skip to main content
Glama

getecoback-climate-weather

klimageraet_testbericht_mode_energieanteil

Read-only

Prüfen, welchen Anteil des protokollierten Stroms ein Werbevergleich für einen ausgewählten Modus erfasst — Check how much of the recorded AC energy a single-mode comparison covers.

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": {
      "gesamt_kwh": "<gesamt_kwh>",
      "modus_kwh": "<modus_kwh>",
      "protokoll_vollstaendig": "<protokoll_vollstaendig>"
    },
    "name": "klimageraet_testbericht_mode_energieanteil"
  }
}

Input Schema

NameRequiredDescriptionDefault
modus_kwhYesDavon dem ausdrücklich beworbenen Modus zugeordneter Strom.
gesamt_kwhYesIm Protokoll erfasster Gesamtstrom.
protokoll_vollstaendigYesStimmen Messzeitraum und Gerät, wurden Umschaltvorgänge und Pausen erfasst?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the computational scope, but it does not explain the return format, edge cases, or whether the result is a ratio or percentage.

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?

The definition is a single front-loaded sentence with a German original and English translation. The bilingual repetition is slightly redundant but not harmful, and no sentence is wasted.

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 low-complexity calculation tool with three fully required and documented parameters, the core intent is covered. However, because there is no output schema, the description should ideally clarify the return value format and any edge-case handling.

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 three parameters are already documented in the schema. The description reinforces the concept of recorded energy and selected mode but does not add syntax, units, or validation details 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 specific check verb and resource: determining the share of recorded AC energy covered by a single advertised mode. It is clear enough to distinguish from general measurement tools, though it does not explicitly contrast itself with any sibling.

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?

It states what is checked but gives no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer the context from the purpose alone.

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