Skip to main content
Glama

getecoback-climate-weather

kochwasser_herd_oder_kanne_transferbilanz

Read-only

Für dieselbe Nutzwassermenge die gemessenen Schritte bis zum Topf vollständig vergleichen — Include observed transfer loss and follow-on heating when comparing kettle versus stovetop.

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": {
      "herd_wh": "<herd_wh>",
      "kanne_wh": "<kanne_wh>",
      "nacherhitzen_wh": "<nacherhitzen_wh>",
      "brauchbare_menge_g": "<brauchbare_menge_g>"
    },
    "name": "kochwasser_herd_oder_kanne_transferbilanz"
  }
}

Input Schema

NameRequiredDescriptionDefault
herd_whYesGemessener Bedarf direkt im Topf bis zum beobachteten gleichen Übergabepunkt.
kanne_whYesGemessene Energie für das Erwärmen in der Kanne.
nacherhitzen_whYesZusätzlich gemessene Energie im Topf nach Übergabe aus der Kanne.
brauchbare_menge_gYesGleiche Menge, die am Ende jedes Vergleichs tatsächlich zur Verfügung stand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare this a safe, closed-world read operation, so the description needn't restate safety. It does add real behavioral content — that observed transfer loss and follow-on heating are included in the comparison — but says nothing about what the computation returns (e.g., a ratio, a delta, a verdict), 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?

Two short, front-loaded sentences with no filler, though the English clause largely restates the German sentence rather than adding information. Slight redundancy is the only structural weakness.

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

Completeness4/5

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

For a four-parameter, fully described calculation tool with read-only annotations, the definition covers the comparison basis and the inclusion of transfer loss. The remaining gap is that the result of the transfer balance is never characterized, which an agent would need to interpret the output.

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 each of the four numeric inputs is already documented, establishing the baseline of 3. The description reinforces the shared-quantity premise (same usable amount) and points at follow-on heating, but adds no units, tolerances, or constraints 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?

The description names a specific operation (comparing measured steps up to the pot for the same useful-water quantity) and the two things being compared (kettle vs. stovetop). It does not differentiate this comparison from the many other comparison-style siblings, but the verb+resource is clear enough that an agent knows what the tool computes.

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?

Usage is only implied: an agent can infer this is for kettle-versus-stovetop energy comparisons with identical usable water amounts. There is no explicit when-to-use/when-not-to-use guidance and no named alternative among the comparison siblings, so the agent must infer the selection condition.

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