Skip to main content
Glama

Stop watching a job

heartbeat_remove
DestructiveIdempotent

Stop watching one job for good. Its check and incident history are deleted, and its ping_url answers 404 at once. It cannot be restored: heartbeat_add makes a new check with a new ping_url. It frees a job slot and works after the plan ended too. Returns deleted: true; an unknown or already removed heartbeat_id answers heartbeat_not_found. To pause alerts and keep the ping_url, use heartbeat_update.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instance_id": "hbt_exampleexampleexample2",
      "heartbeat_id": "hbc_exampleexampleexample2"
    },
    "name": "heartbeat_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYesUtility instance id from buy or list_utilities.
heartbeat_idYesheartbeat id (hbc_...) from heartbeat_add or heartbeat_status.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "heartbeat_id": "hbc_exampleexampleexample2",
      +    "instance_id": "hbt_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes well beyond them: it states what is destroyed (check and incident history), the immediate observable effect (ping_url answers 404 at once), irreversibility, and the slot-freeing side effect. The return contract is spelled out as well — deleted: true on success, heartbeat_not_found for an unknown or already-removed id — which is precisely the confirmation-vs-retry signal an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, no filler, with the destructive consequence front-loaded before the recovery path and the sibling alternative. Each sentence carries distinct information: effect, irreversibility, side benefit, return contract, and the alternative.

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 destructive mutation with no output schema, the description covers what is lost, what the caller sees afterwards, the success and failure signals, and the safer alternative — everything needed to call it responsibly. It stops short only of permission or rate-limit requirements, a minor gap given how much is already disclosed.

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 100%, so both required ids are already documented and a baseline of 3 would be defensible. The description nonetheless adds meaning the schema lacks, by explaining that an already-removed heartbeat_id yields heartbeat_not_found, which tells the agent how to interpret the id's state and how to recover from the error.

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?

A specific verb (stop watching) plus a specific resource (one job/heartbeat) with the permanence qualifier 'for good' doing real work. It also distinguishes itself from heartbeat_add (creates a new check with a new ping_url) and heartbeat_update, so an agent can route without opening any schema.

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?

It names the alternative explicitly: 'To pause alerts and keep the ping_url, use heartbeat_update', which is exactly the decision boundary an agent needs. It adds a non-obvious eligibility condition too ('works after the plan ended'), so there is no ambiguity about when this call is valid.

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.