Skip to main content
Glama

getecoback-climate-weather

heizbuch_kaltphasen_standardisiert

Read-only

Zwei Heizfenster mit gemessenen milden und kalten Tagen über dieselbe Wetterzusammensetzung vergleichen — Compare heat use under a common two-bin weather mix.

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_mild_tage": "<a_mild_tage>",
      "a_kalt_tage": "<a_kalt_tage>",
      "b_mild_tage": "<b_mild_tage>",
      "b_kalt_tage": "<b_kalt_tage>",
      "a_mild_kwh": "<a_mild_kwh>",
      "a_kalt_kwh": "<a_kalt_kwh>",
      "b_mild_kwh": "<b_mild_kwh>",
      "b_kalt_kwh": "<b_kalt_kwh>",
      "gemeinsam_kalt_prozent": "<gemeinsam_kalt_prozent>",
      "bins_gleich": "<bins_gleich>"
    },
    "name": "heizbuch_kaltphasen_standardisiert"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kalt_kwhYesGemessene Heizenergie an kalten Tagen in A.
a_mild_kwhYesGemessene Heizenergie an milden Tagen in A.
b_kalt_kwhYesGemessene Heizenergie an kalten Tagen in B.
b_mild_kwhYesGemessene Heizenergie an milden Tagen in B.
a_kalt_tageYesKalte Tage im Fenster A.
a_mild_tageYesMilde Tage im Fenster A.
b_kalt_tageYesKalte Tage im Fenster B.
b_mild_tageYesMilde Tage im Fenster B.
bins_gleichYesSind Tagesgrenzen, Heizaufgabe und Temperaturgruppen aus beiden Fenstern vergleichbar?
gemeinsam_kalt_prozentYesIn beiden Vergleichen angenommener Anteil kalter Tage in Prozent.

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 agent knows this is a closed, safe computation, and the description does not contradict that. Beyond the annotations the description adds that the comparison normalizes both windows to a shared weather composition ('gemessen' inputs, 'common weather mix'), which is a real behavioral trait. It stops short of saying whether mismatched bins are rejected, which the bins_gleich parameter implies.

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 with the verb early; nothing is padding. The bilingual restatement after the dash is somewhat redundant, but it usefully restates an otherwise dense German compound for non-German readers.

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?

This is a ten-parameter, all-required computation with no output schema, so the description should say what comes back (a standardized comparison figure, a delta, or a verdict) and it never does. The agent also gets no hint about the validity constraint implied by bins_gleich or about what happens when the bins are not comparable.

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 all ten required German parameters are individually documented, so the schema carries the weight. The description reinforces the mild/cold two-bin framing but adds no meaning to gemeinsam_kalt_prozent or bins_gleich that the schema does not already provide; 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 gives a concrete verb plus resource: 'Zwei Heizfenster ... vergleichen' with 'gemessenen milden und kalten Tagen', and it names the analytical frame ('dieselbe Wetterzusammensetzung' / 'common two-bin weather mix'). It is clearly a comparison tool rather than a data-fetch or lookup tool, though it does not distinguish itself from any of the many sibling 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?

The description gives no guidance on when this comparison is appropriate versus alternatives, no prerequisites, and no exclusions. The condition for using it can only be inferred from the phrase 'über dieselbe Wetterzusammensetzung', which is a topic hint, not a usage rule.

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