Skip to main content
Glama

heartbeat

Signed heartbeat for a bond (HMAC-SHA256 with the bond's agent secret)

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": {
      "bond_id": "<bond_id>",
      "seq": "<seq>",
      "ts": "<ts>",
      "sig": "<sig>"
    },
    "name": "heartbeat"
  }
}

Input Schema

NameRequiredDescriptionDefault
tsYes
seqYes
sigYes
bond_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals the signing algorithm and dependency on the bond's agent secret, but does not explain whether the tool records or validates a heartbeat, what side effects occur, what authentication is required, how seq/ts are handled, or what failures look like.

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 description is a single front-loaded sentence fragment with no filler or redundancy. It is efficient, though its brevity contributes to gaps addressed in other dimensions rather than to structural waste.

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

Completeness2/5

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

For a four-required-parameter signed operation with no annotations and no output schema, the description is too thin. It omits the operational effect, required auth setup, sequence and timestamp semantics, and any indication of what a successful or failed call returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all four parameters are required, so the description must compensate. It only hints that bond_id identifies the bond and sig is an HMAC-SHA256 signature, leaving the meanings and formats of seq and ts unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the resource (a bond) and the mechanism (an HMAC-SHA256 signed heartbeat), but lacks an explicit action verb such as submit, record, or validate. It also does not distinguish this tool from siblings like bond_standing, create_bond, evaluate_bond, or witness_status.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus the sibling tools, and it states no prerequisites, exclusions, or expected context. Usage is only weakly implied by the word 'heartbeat'.

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.

Resources