Skip to main content
Glama

getecoback-climate-weather

wasserkocher_warmhalte_innenmessung_grenzpunkt

Read-only

Nach zwei eigenen Messversuchen den zusätzlichen Bedarf des dokumentierten Haltemodus zwischen zwei Zeitpunkten ablesen — Estimate measured marginal kettle holding electricity without extrapolating beyond the observation.

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": {
      "bis_a_min": "<bis_a_min>",
      "bis_b_min": "<bis_b_min>",
      "a_wh": "<a_wh>",
      "b_wh": "<b_wh>"
    },
    "name": "wasserkocher_warmhalte_innenmessung_grenzpunkt"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_whYesBis zur ersten Ablesung seit Haltebeginn gemessene Wh.
b_whYesBis zum späteren Zeitpunkt seit Haltebeginn gemessene Wh.
bis_a_minYesMinuten nach Beginn des gleichen Haltemodus zur ersten Ablesung.
bis_b_minYesMinuten nach Beginn des Haltemodus zur späteren Ablesung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 usefully adds that the estimate is strictly interpolation over observed data with no extrapolation. However, with no output schema it never states what is returned (a Wh delta, a rate, a paired value), which is the main behavioral gap for a computation tool.

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 clauses, German followed by an English gloss, with the core action front-loaded and the no-extrapolation caveat attached immediately. The bilingual duplication costs a little space but is efficient overall.

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?

For a four-parameter computational tool with no output schema, the definition should clarify the shape and unit of the result and what happens if the later reading is not actually later. It covers inputs and the interpolation constraint well but leaves the returned quantity implicit, which is the one thing an agent cannot recover from structured fields here.

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%, and each of the four parameters carries its own German description including units (Wh, minutes since hold start). The tool description only restates that there are two timepoints and two measurements, adding no interpretation of the a/b pairing or ordering constraints beyond what the schema already gives, so the 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 names a specific action ('den zusätzlichen Bedarf ... ablesen' / 'estimate measured marginal ... electricity') and a specific scope (between two timepoints in the documented hold mode, based on two measurements). It is clearly a small derivation tool rather than a measurement or configuration tool, though it never names or contrasts a sibling such as the closing reconciliation tool.

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?

'Nach zwei eigenen Messversuchen' establishes the precondition that two readings must already exist, and 'ohne Extrapolation über die Beobachtung hinaus' acts as an explicit boundary on when the result is valid. What is missing is any routing to an alternative tool when the two readings are absent or when extrapolation is actually required.

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