Skip to main content
Glama

heartbeat

Prove an agent is alive by sending its UUID, keeping status online and earning +0.1 $TRUST per day.

Instructions

Send heartbeat to prove agent is alive. Earns +0.1 $TRUST per day. Keeps agent status 'online'.

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": {
      "uuid": "<uuid>"
    },
    "name": "heartbeat"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesAgent UUID (received at registration)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two concrete side effects: +0.1 $TRUST per day and status set to 'online'. It omits important behavioral details for a heartbeat — required call frequency, whether missing a window flips the agent offline or loses accrued trust, and whether the reward is capped per day.

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?

Three short sentences, action first, then the two effects. Nothing is padded and every clause carries distinct information.

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 trivial one-parameter tool with no output schema, the description covers purpose and effects adequately. The only meaningful omission is cadence and failure consequences, which matters for a heartbeat but is a modest gap given the tool's simplicity.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains that uuid is the agent UUID received at registration. The description adds no further meaning about the identifier, which is acceptable at the baseline for a one-parameter tool.

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 pairs a specific verb and resource ("Send heartbeat") with its intent ("prove agent is alive"), so an agent immediately knows this is an aliveness/ping call. No sibling in the list appears to overlap, though the description never explicitly distinguishes itself from lifecycle tools like check_agent or register_agent.

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 implied rather than stated: calling this keeps status 'online' and accrues $TRUST, so the agent can infer it should be called periodically. However, there is no explicit cadence, no statement of when it must be called, and no note on what happens if it is skipped.

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