Skip to main content
Glama

agent-exec

Take a named lock (paid, x402)

claim_acquire

PAID: lock a key for your own fleet (accountless compare-and-set lease). outcome "acquired": yours; "held": taken, held.mine says if by you. 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_acquire"
  }
}

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. 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 non-read-only, non-destructive, closed-world; the description adds substantial behavior the annotations do not: it is paid, how payment is transmitted (_meta['x402/payment']), which chains and currency are accepted, that an unpaid call returns the price, and that holder is not signed. It falls short of describing lock expiry/release semantics explicitly, relying on the plan enum's implied hold duration.

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

Conciseness5/5

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

Front-loaded with "PAID", then outcome semantics, then payment mechanics, then price. Sentences are short and each carries operational information; the feedback notice is short and clearly bracketed as a side channel.

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?

No output schema exists, and the description compensates by spelling out the outcome envelope ("acquired"/"held" with held.mine). The paid retry protocol and price floor are covered; the main omission is what happens at lease expiry or how to extend, which would matter for a lock tool.

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 documented in the schema. The description only adds that plan determines price and that the concrete table lives in /pricing or service_card, which is a mild supplement rather than new meaning.

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 ("lock a key") plus the mechanism ("accountless compare-and-set lease") and the scope ("for your own fleet", wallet-scoped in the schema). It is clearly distinguishable from generic read/write tools, though it never contrasts itself with the related claim_renew sibling.

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 implied rather than stated: you call it to take a lock, and the description explains the two-step unpaid-then-pay-with-x402 flow and the meaning of "acquired" vs "held". There is no explicit when-not guidance, no note about what to do if the key is already held by you (presumably renew?), and no prerequisites beyond payment.

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.