Skip to main content
Glama

getecoback-climate-weather

stromexport_ueberlappung_entscheiden

Read-only

Zwei Energieexporte desselben Zählers nur bei abgestimmter Überlappungsmenge zusammenführen — Join two exports only when their measured overlap agrees.

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": {
      "export_a_kwh": "<export_a_kwh>",
      "export_b_kwh": "<export_b_kwh>",
      "schnitt_a_kwh": "<schnitt_a_kwh>",
      "schnitt_b_kwh": "<schnitt_b_kwh>",
      "toleranz_kwh": "<toleranz_kwh>",
      "intervall_identisch": "<intervall_identisch>"
    },
    "name": "stromexport_ueberlappung_entscheiden"
  }
}

Input Schema

NameRequiredDescriptionDefault
export_a_kwhYesGesamte kWh im ersten Export.
export_b_kwhYesGesamte kWh im zweiten Export.
toleranz_kwhYesSelbst gewählte maximale Differenz für diese Überlappung.
schnitt_a_kwhYeskWh derselben Überlappung laut erstem Export.
schnitt_b_kwhYeskWh derselben Überlappung laut zweitem Export.
intervall_identischYesPassen Zähler, Start und Ende des verglichenen Überlappungsfensters?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the bar is lower. The description adds the agreement gate, but does not say what the tool emits when the gate fails (error, false, partial result) nor whether it returns a decision versus merged data, and there is no output schema to compensate.

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 sentence with the condition placed prominently before the action, which is the right ordering. The dual German/English rendering duplicates content and costs a little density, but nothing is extraneous.

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 six required numeric parameters, no output schema, and a decision-style tool, the description should specify what a successful versus rejected overlap produces and how tolerance is applied. Those gaps matter for correct invocation, though the parameter names and the stated gate carry most of the load.

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 six parameters are already documented in the input schema and the baseline of 3 applies. The description contributes one genuinely new constraint — that both exports belong to the same meter — but says nothing about how schnitt_a, schnitt_b and toleranz_kwh interact in the comparison.

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 concrete operation (joining two energy exports from the same meter) along with the gating condition (measured overlap must agree), which is far more specific than the name alone. It falls short of a 5 because it never clarifies whether the tool merely decides/validates or actually performs a merge, leaving the name ('entscheiden') and the verb ('zusammenführen') in slight tension.

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 phrase 'nur bei abgestimmter Überlappungsmenge' states a precondition for proceeding, which implies when the tool is applicable. However, it gives no guidance on what to do when the overlap does not agree, and it never names an alternative among the many sibling 'ueberlappung' tools, so an agent must infer routing on its own.

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