Skip to main content
Glama

heartbeat_run

Provider extends its live execution lease within the job deadline; requires both provider bearer authentication and run-scoped claim token.

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": {
      "run_id": "<run_id>",
      "claim_token": "<claim_token>"
    },
    "name": "heartbeat_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
claim_tokenYesShort-lived run-scoped claim token returned by claim_run; keep private

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, open-world behavior, so the bar is lower. The description adds real context beyond them: two distinct auth requirements (provider bearer auth plus a run-scoped claim token) and the deadline-bounded lease semantics. It omits the consequence of a missed heartbeat and any return value, keeping it from a 5.

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?

A single dense sentence with the action front-loaded and the auth prerequisites trailing, with no filler. The phrasing 'Provider extends its live execution lease within the job deadline' is slightly compressed but parses cleanly.

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?

With no output schema and a non-idempotent mutation-like call, the description should say what a successful heartbeat yields or what a rejected one means. Auth and deadline scoping are covered, but the lease-lapse failure mode and response shape are not, leaving a meaningful gap for a tool an agent must call repeatedly.

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 50%: claim_token is documented in the schema (short-lived, returned by claim_run, keep private) and the description only echoes 'run-scoped claim token', while run_id has no description anywhere. The description does confirm both are mandatory, but adds little syntax or meaning beyond the schema.

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 gives a specific verb and resource: the provider 'extends its live execution lease within the job deadline'. That is clearly distinct from claim_run, complete_run, or fail_run. It stops short of naming a sibling to contrast with, so it lands at 4 rather than 5.

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 only implied: the agent can infer this is called while a run is live and must be repeated before the job deadline expires. There is no explicit cadence, no statement of what happens if the lease lapses, and no guidance on choosing this over other run-lifecycle tools.

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