Skip to main content
Glama

Show my heartbeat checks

heartbeat_status
Read-only

List every job (backup, cron run) your heartbeat monitor watches. Works after the plan ended. Status: waiting, up, late (deadline passed, incident about to open), down (incident open until the next ping) or paused. Each has its id (hbc_..., the heartbeat_id the other heartbeat tools take), last_ping_at, expected_by, its secret ping_url and recent incidents with what we told your inbox and owner. owner_email: whether emails reach your owner now. Poll it if no inbox gets alerts. Watched URLs: uptime_status.

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"
    },
    "name": "heartbeat_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYesUtility instance id from buy or list_utilities.
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: +[
      +  {
      +    "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.4/5.0
Behavior5/5

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

Annotations only declare it as a safe read; the description adds substantial context they cannot convey — that it still works after the plan ended, the five status values and what each means operationally ('late' = deadline passed with incident about to open, 'down' = incident open until the next ping), and that each entry carries a secret ping_url and recent incidents. It also explains what owner_email tells the caller about alert delivery.

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?

Purpose is front-loaded in the first sentence, then status semantics, then return fields, then the sibling pointer — a sensible order with no filler. It is dense to the point of being slightly crowded, with several parenthetical asides in one paragraph, but every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return-shape burden and does so: statuses, id, last_ping_at, expected_by, ping_url, recent incidents, and owner_email are all covered, plus the plan-expiry caveat. For a two-parameter read tool, an agent has everything needed to call and interpret it.

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 100%, so instance_id and passport_token are already documented in the schema and the description adds nothing about the inputs. It does clarify the returned hbc_ id as 'the heartbeat_id the other heartbeat tools take,' which is useful cross-tool context but applies to output rather than parameters, so the baseline 3 holds.

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?

States a specific verb and resource: 'List every job (backup, cron run) your heartbeat monitor watches,' with concrete examples of what a heartbeat is. It also distinguishes itself from the sibling uptime_status by scoping that tool to watched URLs, so an agent can pick between the two without opening a schema.

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?

'Poll it if no inbox gets alerts' gives a clear operational trigger, and 'Watched URLs: uptime_status' routes the agent away to the correct sibling for a different resource type. There is no explicit when-not-to-use statement, but the routing signal is present and unambiguous.

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.