Skip to main content
Glama

getecoback-raumklima

heizwaerme_saisonquotient_aus_abschnitten

Read-only

Abgegebene Wärme und Strom zweier Heizabschnitte zunächst summieren und dann vergleichen — Form a weighted heating performance quotient from matching energy totals.

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": {
      "waerme_a_kwh": "<waerme_a_kwh>",
      "strom_a_kwh": "<strom_a_kwh>",
      "waerme_b_kwh": "<waerme_b_kwh>",
      "strom_b_kwh": "<strom_b_kwh>",
      "gleiche_grenze": "<gleiche_grenze>"
    },
    "name": "heizwaerme_saisonquotient_aus_abschnitten"
  }
}

Input Schema

NameRequiredDescriptionDefault
strom_a_kwhYesZugeordneter Strom im ersten Abschnitt.
strom_b_kwhYesZugeordneter Strom im zweiten Abschnitt.
waerme_a_kwhYesGemessene beziehungsweise dokumentierte Nutzwärme im ersten Abschnitt.
waerme_b_kwhYesZugeordnete Nutzwärme im zweiten Abschnitt.
gleiche_grenzeYesNicht überlappende Abschnitte mit gleicher Geräte- und Bilanzgrenze?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety profile is covered. The description adds the two-stage behavior (sum first, then compare) that the annotations cannot express, but it says nothing about what the returned quotient looks like or how the gleiche_grenze flag changes the result, which matters since there is 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 single front-loaded sentence that sequences the operation (sum, then compare) before naming the result. The bilingual phrasing duplicates the same content, which costs a little space without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-parameter computation tool with no output schema, the description leaves the most important thing unspecified: what number or structure comes back and how to interpret it. The domain precondition around a shared balance boundary is left entirely to the boolean parameter's own text rather than being explained.

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 five parameters are already documented with units, bounds and roles. The description's 'matching energy totals' only loosely echoes the gleiche_grenze precondition and adds no format or semantics beyond the schema, so the baseline of 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?

States a concrete verb chain (sum the heat and electricity of two heating sections, then compare) and names the output artifact, a weighted heating performance quotient. It distinguishes the operation from a plain summation, though it never explains what the quotient conceptually represents (a COP-like ratio) or how it differs from sibling heating-energy tools.

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?

There is no explicit when-to-use guidance and no named alternative among the many sibling heating tools. The only usage-adjacent signal is the precondition implied by 'matching energy totals', which an agent must infer from the required parameter gleiche_grenze rather than from the description.

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