Skip to main content
Glama
Sign In

Retasc

by com.retasc
OverviewDiscussionsAdmin

Renew a claim

heartbeat
Idempotent

Extend your lease on a claimed issue during long-silent work. Pass the claim_token when you have it — the fast, unambiguous path. Lost it? Omit it: the same session that claimed the issue is still recognized (RTSC-758), unless the claim was taken over a bare shared workspace key with no per-session key, where identity can't tell callers apart and the real claim_token is still required. Returns the new expiry — a FULL reset, not a top-up: the lease becomes its whole length again (30 minutes behind the retasc mcp-proxy, 2 hours for a claim made with no proxy) from the moment this call lands, whatever was left on it. PREFER checkpoint at long-silence boundaries: it renews identically AND leaves the handoff note that makes a reclaim recoverable. Use a bare heartbeat only when you have nothing worth recording yet. It cannot revive a lapsed lease: once expired you get CLAIM_LOST, even in the window before the sweep runs — lost-token recognition can't fix a lease that's actually gone.

Input Schema

NameRequiredDescriptionDefault
claimTokenNoProves you hold the lease. Omit only if you've lost it (RTSC-758).
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A3.8/5.0
Behavior1/5

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

The description contains useful behavioral detail, including the full lease reset, expiry durations, and `CLAIM_LOST` on expired leases. However, it says the lease is reset from the moment of each call, which conflicts with the annotation `idempotentHint: true`: repeated calls with the same arguments extend the lease further and therefore have an additional effect.

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 front-loaded with the core action and then adds the claim-token fallback, reset semantics, `checkpoint` preference, and expiry behavior. It is somewhat long for a heartbeat tool, but most sentences carry useful operational detail.

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, but the description explains that the tool returns the new expiry. It also covers the key failure mode (`CLAIM_LOST`) and the lease-reset behavior, which is enough for an agent to call and interpret it correctly.

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 50%, and the description thoroughly explains `claimToken`, including when to omit it and the identity exception. It does not explain `identifier` beyond implying it refers to a claimed issue, leaving one of two parameters under-specified.

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?

The description states a specific verb and resource: extending a lease on a claimed issue during long-silent work. It also distinguishes the tool from its closest sibling by explicitly comparing it with `checkpoint`.

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

Usage Guidelines5/5

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

It gives explicit routing guidance: prefer `checkpoint` at long-silence boundaries, and use bare `heartbeat` only when there is nothing worth recording yet. It also states when to pass or omit `claimToken`, including the fallback and the shared-workspace-key exception.

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

All Retasc toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources