Skip to main content
Glama

getecoback-climate-weather

strommessung_abschnitte_verketten

Read-only

Zwei aufeinanderfolgende Strommessabschnitte nur bei tatsächlich gemeinsamen Grenzen summieren — Verify that two cumulative-energy windows are adjacent and avoid double counting.

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": {
      "a_von_min": "<a_von_min>",
      "a_bis_min": "<a_bis_min>",
      "a_kwh": "<a_kwh>",
      "b_von_min": "<b_von_min>",
      "b_bis_min": "<b_bis_min>",
      "b_kwh": "<b_kwh>"
    },
    "name": "strommessung_abschnitte_verketten"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesGemessene Verbrauchsenergie ausschließlich in A.
b_kwhYesGemessene Verbrauchsenergie ausschließlich in B.
a_bis_minYesEnde von A ab demselben Nullpunkt, in Minuten.
a_von_minYesBeginn von A ab gemeinsamem Nullpunkt, in Minuten.
b_bis_minYesEnde von B ab demselben Nullpunkt, in Minuten.
b_von_minYesBeginn von B ab demselben Nullpunkt, in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations already establish this as a side-effect-free local computation, so the description's contribution is the adjacency verification and double-counting warning. It stops short of saying what the tool does when the boundary check fails (error, rejection, or partial result), which is the key behavioral unknown for a validation-style tool.

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?

A single front-loaded sentence pairs the German action clause with an English gloss, which is efficient. The gloss partly repeats the first clause ('adjacent' restates 'gemeinsamen Grenzen') but the redundancy is small and aids comprehension for mixed-language agents.

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?

Six required parameters, no output schema and no nesting mean the description needs to convey the result shape, yet it never says whether the tool returns a summed kWh value, a verification verdict, or an error on non-adjacent input. For a pure computation tool where the output is the entire point, that gap is material.

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 each of the six parameters (a_von_min, a_bis_min, a_kwh, b_von_min, b_bis_min, b_kwh) carries its own German description with units and shared-zero-point context. The description adds no per-parameter meaning beyond restating that A and B are cumulative-energy windows, so the baseline 3 applies.

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 operation ('Zwei aufeinanderfolgende Strommessabschnitte ... summieren') and the precondition for it (shared boundaries), so the agent can tell this is an adjacency-checked aggregation of two energy windows rather than an error, coverage, or forecasting tool. It does not explicitly name a sibling, which keeps it out of the 5 band.

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?

Usage is implied through the condition 'nur bei tatsächlich gemeinsamen Grenzen', which tells the agent when summing is legitimate, but there is no explicit when-not guidance, no statement of what to do when the windows are not adjacent, and no named alternative for overlapping or non-contiguous segments.

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