Skip to main content
Glama

Agent Exchange store

chain_heartbeat

$0.005 via x402: one pre-action heartbeat replaces chain-id + block-tip + block-freshness + gas + fee-history + finality calls. One call covers chain ID + block number + gas, with one round trip and more data. Returns an identity-checked HEALTHY/CONGESTED/STALE verdict across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis and Robinhood Chain.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chain_heartbeat"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase|ethereum|optimism|arbitrum|polygon|gnosis|robinhood (default base)
x_paymentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the most consequential trait for a paid tool — a $0.005 charge via x402 — and enumerates the possible verdicts (HEALTHY/CONGESTED/STALE), which is genuinely useful. But it never explains what happens if x_payment is absent or insufficient, does not describe the returned payload beyond the verdict label, and the term 'identity-checked' is left undefined. Vague marketing phrases like 'more data' substitute for real disclosure.

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

Conciseness3/5

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

The cost and aggregation claim are front-loaded, which is good. But two consecutive sentences restate the same point ('replaces chain-id + block-tip + ... + finality calls' followed by 'one call covers chain ID + block number + gas'), and the closing chain list inflates length. Tightening to one aggregation sentence plus the verdict/chain facts would strengthen it considerably.

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

Completeness3/5

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

For a two-parameter, no-output-schema, no-annotation paid tool, the description should compensate more. It covers what the tool aggregates and the verdict vocabulary, but omits the response shape (which fields are returned alongside the verdict), payment failure behavior, and any freshness window defining 'STALE'. Adequate to select the tool, insufficient to invoke it confidently.

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 coverage is only 50%: the chain parameter is documented with accepted values and a default, but x_payment has no description anywhere. The description partially compensates by listing the supported chains (Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis, Robinhood Chain) and by linking payment to x402, but it does not explain the required format or placement of the payment token. Partial compensation for a real gap.

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 states a specific composite purpose: a 'pre-action heartbeat' that aggregates chain ID, block tip, gas, fee history and finality into a single HEALTHY/CONGESTED/STALE verdict. It explicitly names the individual sibling calls it replaces (chain-id, block-tip, gas, fee-history, finality), so an agent can distinguish it from chain_id, chain_gas_price, chain_fee_history and chain_block_header. It loses a point only because the framing is marketing-flavored ('one round trip and more data') rather than a crisp definition.

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?

'Pre-action heartbeat' implies the context of use: call once before performing an on-chain action instead of fanning out to individual read tools. However, it never states when NOT to use it — e.g. when an agent only needs a single field and should call chain_id or chain_gas_price directly — nor does it mention prerequisites such as holding credits or a payment header. Usage is inferable but not spelled out.

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