Skip to main content
Glama

heatpump_set_confirm

Confirm a proposed heat pump change only after the owner says yes, using the token from the latest request, then verify the unit shows the change.

Instructions

Make it, after a yes. Send the change asked about. Call only with the token from the most recent heatpump_set_request, and only after the owner has said yes to its question. A wrong or old token is refused and cancels the question. The unit is read back afterwards: success is true only when it shows the change. Read 'say' aloud.

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": {
      "token": "<token>"
    },
    "name": "heatpump_set_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

readOnlyHint=false already signals a mutation, and the description adds substantial behavior beyond it: token freshness validation, cancellation of the pending question on bad tokens, and a post-write read-back where success is true only if the unit actually reflects the change. That is exactly the kind of verification and side-effect detail annotations cannot express.

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?

Short and mostly front-loaded: precondition, then failure mode, then verification. The elliptical opener 'Make it, after a yes' and the trailing 'Read "say" aloud' are slightly cryptic, but each sentence carries operational information and nothing is redundant.

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 one-parameter mutation with an output schema, the description covers the prerequisites, the consequence of a stale token, and how to interpret the success flag, so an agent can call it without guessing. The only soft spot is that 'Read "say" aloud' is not explained, leaving the response field's handling implicit.

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?

Schema coverage is 0% and the only field is a bare 'Token' string, so the description must carry the meaning. It does: the token must come from the most recent heatpump_set_request, corresponds to its pending question, and must be the current one or it is refused. It does not describe token format, but freshness and provenance are the semantics that matter here.

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 makes clear this applies/commits the change that was previously asked about via heatpump_set_request, and it distinguishes itself from that sibling by requiring its token. The opening phrase 'Make it, after a yes' is cryptic on its own, but the following sentences ('Send the change asked about') anchor a specific verb and resource.

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

Usage Guidelines5/5

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

Explicit preconditions are given: call only with the token from the MOST RECENT heatpump_set_request and only after the owner has answered yes to that question. It also names the failure case (wrong or old token is refused and cancels the question), which tells the agent what not to do and what happens if it does.

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