Skip to main content
Glama

agent-exec

by org.448c.agent-exec
OverviewDiscussionsAdmin

Take a named lock (paid, x402)

claim_acquire

PAID: atomically win a caller-named key for your own fleet -- an accountless compare-and-set. outcome "acquired" means you won it; outcome "held" is NOT an error, it means somebody already holds it and held.mine says whether that somebody is you -- the signal that stops a crash-resume or a duplicated retry doing an irreversible action twice. Keys are scoped to the PAYING WALLET: one payer's keys are invisible to every other payer. Inspect it with claim_read, give it up early with claim_release, extend it with claim_renew. Call it once without payment to receive the price as an x402 PaymentRequired (Base USDC, and Solana USDC where offered); call it again with a signed payment in _meta['x402/payment'] to complete it. The receipt comes back in _meta['x402/payment-response']. No account, no API key. Complaints, questions, quote requests, or a service you wish we had: POST /feedback on this host -- free, no account. Every report is read and analysed daily; there is no individual reply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes1..256 UTF-8 bytes, no '/' character -- the name you want to hold, scoped to your own wallet.
planYesWhich plan to buy; it sets both the hold duration and the price. See GET /pricing or the service_card tool for the live table.
holderYes1..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

A4.9/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false. The description carries the full burden and does so thoroughly: explains it's paid, atomic, compare-and-set, scoped to paying wallet, outcomes 'acquired' vs 'held', and the payment/receipt mechanism. No contradictions with annotations; adds crucial behavioral context.

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?

Though long, every sentence earns its place: core purpose is front-loaded, then outcomes, sibling routing, payment flow, and feedback. No redundancy; structured logically from core behavior to supporting details.

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?

Complete for a paid, multi-step tool. Covers payment flow, outcome semantics, wallet scoping, alternatives, and feedback. No output schema exists, but description explains receipt location and outcome fields. An agent has everything needed to invoke and interpret results.

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 covers all three parameters with descriptions (100% coverage). The description adds meaning beyond schema: for 'key' it clarifies wallet scoping, for 'plan' it links duration and price, for 'holder' it explains it identifies the process and is not signed. This extra context raises it above baseline 3.

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: 'atomically win a caller-named key' and identifies it as a paid compare-and-set lock. It distinguishes from siblings by explicitly mentioning 'PAID' and naming related tools (claim_acquire_free, claim_read, claim_release, claim_renew). The purpose is unambiguous.

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?

Provides explicit two-step payment flow: call without payment to get price, then with signed payment. Clarifies that outcome 'held' is not an error and explains the signal to stop duplicate retries. Names sibling tools for inspection, release, and renewal, and gives feedback channel. No ambiguity about when to use this vs alternatives.

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

All agent-exec 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