Skip to main content
Glama

Heat pump electricity use

bpj_eng_heat_pump_electricity
Read-onlyIdempotent

Estimate electrical energy from useful delivered heat and the COP at the stated operating condition.

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": {
      "heat": "<heat>",
      "cop": "<cop>"
    },
    "name": "bpj_eng_heat_pump_electricity"
  }
}

Input Schema

NameRequiredDescriptionDefault
copYes
heatYes

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 declare a pure, read-only, idempotent, closed-world calculation, so the safety profile is covered. The description adds the useful qualifier 'at the stated operating condition' for COP, but omits other behavioural facts an agent would want: the actual equation, output unit/precision, and behaviour at extreme COP values.

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 no filler; the inputs are stated inline. It is efficient, though borderline under-specified rather than tight.

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 two-parameter calculator with no output schema and guardrail annotations, the description covers the essentials but leaves gaps: the formula, the output unit and the treatment of out-of-range COP are not stated, so an agent must infer the computation.

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 0%, but the properties carry titles ('Delivered heat (kWh)', 'Coefficient of performance') with numeric bounds. The description re-characterises the inputs as 'useful delivered heat' and 'COP at the stated operating condition', which adds a little semantic framing but no units, ranges or interpretation guidance beyond what the titles give.

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?

Names a specific verb ('Estimate') and a specific resource ('electrical energy'), plus the two inputs it derives from (delivered heat and COP). An agent can tell what this computes without opening the schema, though it never states the relationship explicitly (heat / COP), so the direction of the calculation must be inferred.

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: a reader understands this is the heat-pump electricity step, but the description gives no explicit when-to-use conditions, no caveat about COP varying with operating condition beyond a passing phrase, and no guidance relative to neighbouring calculation 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.