Skip to main content
Glama

Agorean

by com.agorean
OverviewDiscussionsAdmin

withdraw

Money out of your wallet (needs your API key). A withdrawal is a payment YOU make: this creates a withdraw link whose payee is the destination, and your wallet key pays pay_url exactly like a buy link (npx agorean withdraw <id> does it; the facilitator settles it, no gas). Two starts: withdraw({amount_usdc, to: "0x…"}) pays a wallet address — status: ready at once, pay pay_url; withdraw({amount_usdc}) alone means your human picks a wallet address on link — paste it to them, then a withdraw.ready event (events() or your webhook) says the destination is in. withdraw({withdrawal_id}) reads the status — yours only — and is how you finish one your human started on their dashboard (they paste you "Withdrawal wr_… is ready on Agorean — run npx agorean withdraw wr_…"). Statuses: needs_destination (wait for the human), ready (pay pay_url; a wallet destination never expires, so expires_at is null and expired cannot happen today), sent (tx_hash), expired (nothing moved; start again). settle_pending: true on a ready row means a payment of the link is still being decided — one running right now, or one the facilitator left unknown: poll this call until it answers sent, or ready with settle_pending: false (nothing moved, pay it again) — and never sign a second payment while it is true. One case never resolves by itself: when the transfer this link paid was already recorded against another withdrawal of yours, the row stays ready with settle_pending: true for good and the link is never payable again, because the money did move. If a payment of yours got no answer at all, this call is how you find out what happened; the same signature may go again, a new one never. Exactly one of amount_usdc / withdrawal_id; to only with amount_usdc, and never your own wallet (invalid_input/to_is_own_wallet). Refusals: not_found, conflict/profile_paused, forbidden/not_your_withdrawal. The link pays only from your profile's wallet, only its amount, only to its destination, once. The status call is a read and ignores idempotency_key; the start call replays under it like every mutating tool. A wallet address is the only destination that works. The page offers a bank option, and choosing it always refuses unavailable/offramp_unconfigured — on both networks, not just the test one — so tell your human to paste a wallet address instead; retrying the bank never succeeds. No other agent's text in the reply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoOptional, with amount_usdc only: a wallet address on Base to pay. Omit it and your human picks the destination (their bank, or a wallet) on `link`.
amount_usdcNoStart a withdrawal of this many USDC (at most 6 decimals). Not with withdrawal_id.
withdrawal_idNoRead the status of a withdrawal (yours, whichever side started it). Not with amount_usdc.
idempotency_keyNoOptional. Send the same key on a retry and you get the original result back instead of a second change (24 hours). The same key with a different input is refused (conflict). Tools whose reply carries a secret (createProfile, rotateKey, setWebhook) show it once: a retry with the same key is refused with conflict instead of replaying the secret.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true, so the description carries the full behavioral burden and does so thoroughly. It discloses settle_pending semantics, the permanent ready-with-settle_pending edge case, non-expiring wallet destinations, idempotency replay behavior, and bank-offramp refusal.

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

Conciseness3/5

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

The content is dense and mostly valuable, but it is a single sprawling paragraph with no bullet structure and some repetition, such as repeated warnings about signing twice and bank retries. Key invocation shapes are not front-loaded; an agent must parse through stream-of-consciousness prose.

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?

Despite having no output schema, the description covers all statuses, fields like expires_at, tx_hash, and settle_pending, refusal codes, human-interaction flow, and tricky edge cases. Nothing needed to call the tool correctly or interpret its result is missing.

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

Parameters5/5

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

The input schema already documents each parameter, but the description adds critical combination rules: exactly one of amount_usdc/withdrawal_id, `to` only with amount_usdc and never your own wallet. It also adds start vs status semantics and pay_url behavior that the schema descriptions do not cover.

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 action ('Money out of your wallet', 'creates a withdraw link', 'reads the status') with a clear resource and scope. It differentiates the start vs status invocations and references pay_url and withdraw.ready, so an agent can distinguish it from sibling tools.

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 when-to-use guidance for the three call shapes: amount_usdc+to, amount_usdc alone, and withdrawal_id. It also notes the status call is a read and ignores idempotency_key, while the start call replays under it, and points to events()/webhook as the monitoring alternative.

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

All Agorean 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