Skip to main content
Glama

getecoback-raumklima

punktwaerme_arbeitsziel_wechsel_energieabschnitt

Read-only

Gemessene Zusatzwärme zweier verschieden langer Arbeitsarten nach fertiggestellten Einheiten und nicht nach reiner Heizzeit lesen — Compare task-specific energy per completed work item under explicit time and output limits.

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_wh": "<a_wh>",
      "b_wh": "<b_wh>",
      "a_einheiten": "<a_einheiten>",
      "b_einheiten": "<b_einheiten>",
      "a_min": "<a_min>",
      "b_min": "<b_min>",
      "gleichwertige_ergebnisse": "<gleichwertige_ergebnisse>"
    },
    "name": "punktwaerme_arbeitsziel_wechsel_energieabschnitt"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_whYesGemessene Zusatzenergie des ersten vollständig beobachteten Arbeitsabschnitts.
b_whYesGemessene Zusatzenergie des späteren Vergleichsabschnitts.
a_minYesDokumentierte tatsächliche Arbeitsminuten in A.
b_minYesDokumentierte tatsächliche Arbeitsminuten in B.
a_einheitenYesZahl vollständig erledigter gleichartiger Arbeitseinheiten in A.
b_einheitenYesZahl vollständig erledigter Arbeitseinheiten in B.
gleichwertige_ergebnisseYesGleichartige Aufgaben und vergleichbares, planmäßig sichtbares Endergebnis?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

While annotations handle safety (read-only), the description provides essential operational context by defining the specific business logic of the calculation—that the comparison must be based on task-specific output metrics rather than simple duration, guiding the agent's mental model of the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is highly concise, using a single sentence (followed by an accurate translation) to encapsulate the complex business logic efficiently without redundancy.

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

Completeness5/5

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

Given the high parameter count and the complexity of the comparison, the description is highly complete by clearly articulating the exact metric and condition under which the analysis should be performed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema provides full coverage, the description defines the high-level semantic goal of the inputs: comparing task efficiency based on output units under time limits, adding necessary context beyond the mere variable definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the function as reading auxiliary heat measurements for two tasks and compares them based on completed work units, distinguishing this from a simple time-based comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It specifies the crucial methodology for usage: energy must be calculated per completed work item, not per pure heating time. This sets a clear constraint on how the agent should conceptualize the inputs.

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