Skip to main content
Glama

heatpump_status

Read-only

Reads current heat pump status without changing settings, reporting power, mode, set temperature, room and outdoor temperatures, and fan speed; can speak the reading aloud.

Instructions

Read the unit; no change. Say whether the heat pump is on, its mode (heat, cool, dry, fan, auto), the temperature it is set to, the room and outdoor temperature, and the fan speed. A reading is reused for 30 seconds. Read 'say' aloud.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "heatpump_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it while adding non-obvious behavior: results are cached for 30 seconds, so repeated calls may return a stale reading. It also indicates the response is meant to be spoken ('Read say aloud'), which is genuine delivery context. It says nothing about failure modes (offline unit, unsupported mode), which keeps it short of a 5.

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?

The scope constraint is front-loaded and each sentence adds information (purpose, returned fields, caching, delivery). The fragmentary phrasing and the cryptic closing instruction 'Read say aloud' cost some clarity but not much length.

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 zero-parameter, read-only tool with an output schema, this covers purpose, returned fields, caching, and output medium adequately. Missing are any caveats about the unit being unreachable or a mode not being reported, which an agent might need to interpret an empty or partial reading.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the schema is trivially complete. The description correctly spends no space on inputs and instead covers what the no-argument call yields.

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 uses a specific verb-plus-resource framing ('Read the unit... Say whether the heat pump is on') and enumerates the exact fields returned (mode, setpoint, room/outdoor temperature, fan speed). 'No change' immediately separates it from the heatpump_set_request/set_confirm siblings without needing their schemas.

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?

The opening 'no change' and the enum of modes set a clear context: use this for observation only, not for altering settings. It does not explicitly name the set siblings as the alternative path, so the routing signal is implicit rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.