Skip to main content
Glama

arcgate

by dev.arcgate
OverviewDiscussionsAdmin

accountTier

Sets the tier the account's next accountRenew runs at, up or down. The tier, units and limits do not change until that renewal.

  • Cost: Free. Signed by the owner over method POST, path /account/v1/<address lowercased>/tier and the body {"tier": ...}. The ARCGATE-KEY header does not authorize it: a call with only a key is a 401 signature_required.

  • Inputs: address (path), any letter case, and tier (body), one of the paid tiers. The account's current tier cancels a change already scheduled.

  • Returns: accountId, tier, the account's tier now, scheduledTier, the tier the next renewal runs at (null after a cancel), and periodEnd, when renewal opens. A lapsed account or one in grace schedules the same way, and a lapse keeps the schedule.

  • Errors:

    • 404 account_not_found: the address has no account.

    • 409 tier_does_not_fit: a downgrade whose target tier holds fewer boxes, watches, screens or agent screens than the account's linked boxes have. Nothing is scheduled. The body names the tier, its limits and what has to go in toRemove. Held messages are not checked, and an upgrade is never refused.

  • Next:

    • accountRenew: pay for the next period once periodEnd has passed, at the scheduled tier.

    • accountStatus: read scheduledTier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierYesThe tier the next `accountRenew` runs at, up or down. The account's current tier cancels a change already scheduled.
addressYesThe account owner's address, any letter case. One account per address, and a signed request must be signed by it.
agentSignatureNoThe owner's EIP-712 signature over this request, as the AGENT-SIGNATURE, AGENT-NONCE and AGENT-EXPIRY headers carry it over HTTP. Sign the typed data `AccountRequest` (not `AgentRequest`) with fields `origin` (the API's base URL with no trailing slash: the URL this request is sent to less its path, for example `https://api.arcgate.dev`; over MCP the same, not the /mcp URL), `address` (the owner), `method`, `path`, `bodyHash`, `nonce` and `expiry`, in that order. A signature made for another deployment's origin is a 401 invalid_signature, under the domain {name: "arcgate", version: "1"} with no chainId (a wallet that can only sign with one may add the chainId of the chain this deployment serves). The `path` is the request path with the address lowercased. The `bodyHash` is the keccak256 of the canonical JSON of the body you send (sorted keys, no whitespace), or of no bytes when there is none. Each nonce is accepted once per owner. Omitting it is a 401 signature_required, never a charge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 well: it declares the operation free, states it must be owner-signed over a specific method/path/body, and warns that the ARCGATE-KEY header alone yields 401 signature_required. It also documents the 409 tier_does_not_fit downgrade refusal (with what the body names), held-message exemption, upgrade-never-refused rule, and lapse/grace scheduling behavior.

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 labeled sections (Cost, Inputs, Returns, Errors, Next) front-load the core behavior and make the dense content scannable. It is long, and the signature details in the description partly overlap the schema's agentSignature documentation, but the length is defensible for a signed, error-prone mutation.

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?

For a three-parameter, nested-object, signed mutation with no output schema, the description covers return fields (accountId, tier, scheduledTier, periodEnd), typed error codes with causes, cancellation semantics, and downstream tool handoffs. Nothing an agent needs to invoke it correctly 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 description coverage is 100% and the parameter descriptions are themselves unusually detailed (tier, address, and the full AccountRequest signature recipe), so the schema does the heavy lifting. The description's "Inputs" bullet (address any letter case, tier one of the paid tiers, current tier cancels a pending change) largely restates that, adding little beyond the baseline.

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?

"Sets the tier the account's next `accountRenew` runs at, up or down" is a precise verb+resource statement, immediately qualified by the crucial scoping fact that units and limits do not change until renewal. This distinguishes it cleanly from siblings like accountRenew (which pays) and accountStatus (which reads the schedule).

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?

The "Next" section explicitly routes the agent to accountRenew (pay once periodEnd passes) and accountStatus (read scheduledTier), which gives clear sequencing context. However it never states when NOT to call this tool or frames these as alternatives the agent must choose between, so it stops short of the top tier.

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