Skip to main content
Glama

MCPFax Agent Continuity

by com.mcpscores
OverviewDiscussionsAdmin

Extend a lease you hold

lease_renew
Idempotent

Extend a lease you still hold, using the fence token you were given. FREE. Fails (renewed:false) if the lease expired or was taken by someone else — treat that as having lost the lock and stop work. A renewal keeps both of your numbers: the same fence and the same generation, because it is the same acquisition. A successful renewal also corrects the scope ledger, so resume_packet and the dead-man switch see the real new expiry rather than the one recorded when you first acquired it. FREE — this tool never charges. Authenticate with Authorization: Bearer , or pass agent_key as an argument if your host cannot set headers. Equivalent HTTP route: POST /v1/lease/renew.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesThe leased key. Example: 'queue/orders'.
fenceYesThe fence token from lease(). Required, and only the caller lease() handed it to has it — it is drawn independently for each acquisition, so it cannot be derived from an earlier one and the example below is a shape, not a usable value. Example: '3170294857216913'.
holderYesThe same holder id you acquired with. Example: 'worker-3-6f2a91'.
agent_keyNoYour agent_secret, if your MCP host cannot set the Authorization header. Prefer the header.
ttl_secondsNoNew lifetime from now. Default 60, max 3600. Example: '60'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agent_key / examples
      Added value: +[
+  "the agent_secret that register returned"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / fence / examples
      Added value: +[
+  3170294857216913
+]
    • addedInput schema / properties / holder / examples
      Added value: +[
+  "worker-3-6f2a91"
+]
    • addedInput schema / properties / key / examples
      Added value: +[
+  "queue/orders"
+]
    • addedInput schema / properties / ttl_seconds / examples
      Added value: +[
+  60
+]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond annotations: it is free, it fails with renewed:false on expiry or takeover, it preserves fence and generation, and it corrects the scope ledger so downstream systems see the real expiry. This is exactly the kind of operational nuance annotations like idempotentHint do not capture.

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 longer than average but every sentence adds operational value: free, failure semantics, token preservation, ledger correction, and auth. The FREE point is repeated, which is mild redundancy, but the structure is front-loaded with the core action and most critical caveats first.

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 lease-renewal tool with no output schema, the description covers the failure response, side effects, authentication, and HTTP route. It does not spell out the successful response shape in detail, but it provides enough for an agent to invoke correctly and interpret the key failure case.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description goes further by explaining that the fence token is drawn independently per acquisition and cannot be derived or reused from an earlier lease, which adds real meaning beyond the schema. It also clarifies the agent_key parameter's role as a fallback when headers cannot be set.

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?

States a specific verb and resource: 'Extend a lease you still hold' with the fence token. This clearly distinguishes it from lease_release (letting go) and lease (acquiring), and the title reinforces the same meaning without being a pure tautology.

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

Usage Guidelines4/5

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

Describes when renewal succeeds and when it fails: if the lease expired or was taken, treat it as lost and stop work. It implies the appropriate use case—extending a lease you still hold—and warns about the lost-lock condition, though it does not explicitly name sibling alternatives or state 'use this instead of X'.

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

All MCPFax Agent Continuity toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources