Skip to main content
Glama

arcgate

by dev.arcgate
OverviewDiscussionsAdmin

accountRenew

Starts the account's next period of 30 days at the tier scheduled with accountTier, else the account's own tier, and restores a lapsed account.

  • Cost: The price of the tier the renewal runs at (account.tier.<tier>.price, read live), paid over x402: the tier scheduled with accountTier, else the account's own. Anyone may pay, not only the owner. No key, no signature and no body: the tier is the owner's, never the payer's choice. A payment made at a price asked before the owner scheduled another tier is a 402 again, or a 409 renewal_repriced when the tier changed while the payment was being verified, and settles nothing either way.

  • Inputs: address (path), any letter case. No body.

  • Returns: accountId, tier, the new period's periodStart, periodEnd and graceEnd, and its units. A renewal while the account is in grace starts the new period at the old periodEnd, so no day is lost. After the lapse it starts at the time of the renewal. Leftover units are discarded. Credit is kept.

  • Errors:

    • 400 invalid_request: the request has a body. A renewal takes none. Nothing settles.

    • 404 account_not_found: the address has no account. Create one with accountCreate. Nothing settles.

    • 409 period_running: the period has not ended, so there is nothing to renew yet. The body names periodEnd. Renew from then, until the grace ends. Nothing settles.

    • 409 renewal_repriced: the tier the renewal runs at changed after it was priced, by an accountTier call or a price change while the payment was verified. The body names the tier it runs at now. Ask again and pay that price. Nothing settles.

    • 503 notifier_unavailable: the account's tier could not be read. Nothing settles.

  • Next:

    • accountStatus: read the new period, the units and the state.

Costs the account's tier's price: 4.99 USDC for agent; 49 USDC for starter; 149 USDC for builder; 499 USDC for growth; 1499 USDC for scale; the exact amount for the account's tier comes back in the payment-required result. Payment goes in params._meta["x402/payment"]; use an x402-aware MCP client (see https://docs.arcgate.dev/#arcgate/description/mcp-for-agents).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe account owner's address, any letter case. It names the account to renew; the payer may be any address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses the live-read price, the x402 payment path and that no key/signature/body is needed, that the tier is the owner's and never the payer's choice, and the exact settlement semantics of grace vs. lapsed renewals (leftover units discarded, credit kept, no day lost). It enumerates every error code with the condition and settlement outcome, which is precisely the behavioral context an agent needs for a paid mutation.

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?

Bold section headers (Cost, Inputs, Returns, Errors, Next) make it scannable and front-loaded, and the length is justified by the payment complexity. It loses a point for repetition: 'Nothing settles' recurs five times and the address letter-case/payer point appears in both description and schema.

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?

There is no output schema and no annotations, yet the description enumerates the returned fields (`accountId`, `tier`, `periodStart`, `periodEnd`, `graceEnd`, `units`), the pricing table, and the full error surface. Nothing an agent needs to invoke or recover from this call is missing.

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 coverage is 100% and the `address` description already documents letter-case tolerance and that the payer may be any address, so the schema does the heavy lifting. The description's Inputs section largely restates the path parameter; the baseline 3 is appropriate when the schema is this complete.

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?

Opens with a specific verb and resource: it starts the account's next 30-day period and restores a lapsed account. It explicitly distinguishes itself from siblings by naming `accountTier` (which sets the scheduled tier) and `accountCreate` (used when no account exists), so an agent can tell it apart without opening another schema.

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?

States the preconditions clearly (the period must have ended, otherwise 409 `period_running` names `periodEnd`), tells the agent how to recover from repricing (ask again and pay the new price), and routes to the follow-up tool (`accountStatus`). It also notes who may invoke it (anyone, not just the owner), leaving little to inference.

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

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