Skip to main content
Glama

getecoback-climate-weather

testvoraussetzung_inklusive_und_exklusive_mengen

Read-only

Prüfe, ob zwei Verbrauchszahlen dieselben Bestandteile eines Testlaufs enthalten — Reconcile consumption figures with different test boundaries

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": {
      "wert_a_kwh": "<wert_a_kwh>",
      "wert_b_kwh": "<wert_b_kwh>",
      "nur_a_teil_kwh": "<nur_a_teil_kwh>",
      "nur_b_teil_kwh": "<nur_b_teil_kwh>",
      "abgrenzung_und_gleiche_aufgabe": "<abgrenzung_und_gleiche_aufgabe>"
    },
    "name": "testvoraussetzung_inklusive_und_exklusive_mengen"
  }
}

Input Schema

NameRequiredDescriptionDefault
wert_a_kwhYesDokumentierter Gesamtwert A in kWh
wert_b_kwhYesDokumentierter Gesamtwert B in kWh
nur_a_teil_kwhYesBelastbar erfasster Bestandteil in A außerhalb des gemeinsamen Umfangs
nur_b_teil_kwhYesBelastbar erfasster Bestandteil in B außerhalb des gemeinsamen Umfangs
abgrenzung_und_gleiche_aufgabeYesEin- und Ausschlüsse sind vollständig gemessen und die gemeinsame Aufgabe stimmt überein

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 state readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the conceptual model of comparing components across differing test boundaries, but it does not explain the decision outcome, mismatch handling, or return semantics.

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 no wasted explanation. The German/English restatement is slightly redundant but still compact and useful for clarity.

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?

Given five required numeric parameters and no output schema, the definition is only partially complete. It explains the comparison concept but leaves the result format and expected output of the check unspecified.

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 the five parameters are already fully documented in the schema. The description mentions two consumption figures and test boundaries but adds no format or interpretation details beyond the schema baseline.

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 states a specific check: whether two consumption figures contain the same components of a test run, with a parenthetical clarifying reconciliation across different test boundaries. The verb and resource are clear, but no sibling tool is named or differentiated.

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 'Reconcile consumption figures with different test boundaries' implies when the tool is useful, but there is no explicit when-to-use guidance, no when-not guidance, and no reference to alternatives among the many sibling tools.

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