Skip to main content
Glama

Extend a lock you hold (paid, x402)

claim_renew

PAID: extend a key lock you hold, keeping it. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: from $0.0100 USDC.

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": "claim_renew"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo1..256 UTF-8 bytes, no '/' character -- the name you want to hold, scoped to your own wallet.
planNoWhich plan to buy; it sets both the hold duration and the price. See GET /pricing or the service_card tool for the live table.
holderNo1..256 UTF-8 bytes -- an id identifying which of your own processes is acting. It is not signed; the signature proves the wallet, not the process.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
      -  "key",
      -  "holder",
      -  "plan"
      -]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare a non-read-only, non-destructive, closed-world mutation; the description adds substantial context beyond that: the tool is paid, price starts at $0.0100 USDC, payment is settled via x402 on a listed set of chains, and the first unpaid call is a price quote rather than a mutation. It leaves open what happens if the lock is gone or the payment fails, but that gap is modest against the annotation baseline.

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?

Front-loaded with the verb and paid qualifier, then the payment mechanics; every sentence carries operational information and there is no filler. The chain enumeration is slightly dense but justified because chain selection matters for payment.

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?

Covers the payment flow, price floor and a feedback channel, which is meaningful for a paid mutation with no output schema. What remains is the core semantic question for an 'extend' operation: whether the chosen plan adds to remaining hold time or resets it, and what the unpaid response contains is only partially implied.

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 100%, so key, plan and holder are already fully documented in the schema, including the plan enum and the holder's unsigned-process semantics. The description adds only indirect meaning by tying price to plan ('Price: from $0.0100 USDC'). Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb and resource: 'extend a key lock you hold, keeping it.' The scope qualifier ('a lock you hold') distinguishes it from an acquire-style sibling without naming one. It stops short of explicitly contrasting with claim_acquire, so it is clear but not sibling-differentiating in the strongest sense.

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?

Gives concrete procedural guidance for the two-step paid flow: call unpaid to get the price, pay via x402 in _meta['x402/payment'], then call again. It also states the prerequisite implicitly ('a lock you hold'). It does not say what to do if the lock has expired or been lost, or name the acquire alternative, so exclusions are absent.

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