Skip to main content
Glama

getecoback-raumklima

stromexport_einheit_metadaten_abgleichen

Read-only

Explizit deklarierte Wh- und kWh-Exportspalten vor einer Zusammenführung gegenprüfen — Normalize documented energy units while leaving unknown labels unresolved.

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_wert": "<a_wert>",
      "a_einheit": "<a_einheit>",
      "b_wert": "<b_wert>",
      "b_einheit": "<b_einheit>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "stromexport_einheit_metadaten_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_wertYesExportwert A für dieselbe Energiemenge.
b_wertYesExportwert B für dieselbe Energiemenge.
a_einheitYesEnergieeinheit laut dokumentiertem Export A.
b_einheitYesEnergieeinheit laut dokumentiertem Export B.
vergleichbarYesHandelt es sich nachweislich um dasselbe Register und Intervall?

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. The description adds one real behavioral fact beyond that: unknown labels are left unresolved rather than guessed. It does not say what the call actually yields (normalized value, comparison verdict, or error) despite there being no output schema.

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 compact two-clause definition with the scope constraint front-loaded. The German/English duplication of the same content is slightly redundant, but nothing is padded and the key qualifier appears first.

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 five-required-parameter comparison tool with no output schema, the description covers the input side adequately but never describes the return result. An agent knows when to call it and what to pass, but not what to expect back, which is a meaningful gap for a cross-check operation.

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%, so the schema already documents all five parameters including the wh/kwh/fehlend enums and the vergleichbar flag. The description corroborates the unit vocabulary and the "unresolved" handling of unknown labels, which maps loosely to 'fehlend', but adds no format or boundary detail 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?

States a specific verb and resource: cross-check ("gegenprüfen") explicitly declared Wh/kWh export columns before a merge. The scoping phrase "Explizit deklarierte ... Exportspalten" signals this is not a general unit converter and implicitly separates it from merge/summing siblings, though no sibling is named directly.

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 "vor einer Zusammenführung" gives a clear usage moment (pre-merge validation), which is genuine context. However, it offers no explicit exclusions or pointer to an alternative when values are not comparable or labels are missing, leaving the agent to infer.

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