Skip to main content
Glama

arcgate

by dev.arcgate
OverviewDiscussionsAdmin

accountStatus

Reads an account's tier, its period, the units used and left, and its limits.

  • Cost: Free. Signed by the owner over method GET, path /account/v1/<address lowercased>/status and no body (the hash of no bytes), or sent with the account's key in ARCGATE-KEY.

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

  • Returns: tier, scheduledTier (the tier the next renewal runs at, null when none is scheduled), periodStart, periodEnd and graceEnd, state (running, grace or lapsed), units (period, used and left), credit (the overage balance in USDC base units and per1000Units, what 1,000 units cost from it at the tier now), limits, which are the tier's as the config holds them now, linkedBoxes (each box's address, when it was linked and the id of the key that linked it, null for the owner's signature) and notices, what happened to the account in this period that its owner is told of, newest first. A box_linked notice names the box and the key. A units_warning or units_used_up notice gives the period's units, how many were used and the credit then. A period_ending_first or period_ending_last notice gives the periodEnd and the graceEnd. A lapsed notice gives them too, the credit and each linked box with the allowance it runs on now.

  • Errors:

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

    • 403 key_wrong_account: the key belongs to another account than the address in the path.

  • Next:

    • tradeSearch: spend the units with the key.

    • boxLink: link a box to the account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.1/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 declares the operation is free, specifies the exact auth mechanism (owner EIP-712 signature over GET with the given path and empty body, or an ARCGATE-KEY header), and documents both failure modes (404 account_not_found, 403 key_wrong_account). This is exactly the behavioral context an unannotated read tool needs.

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?

The first sentence front-loads the purpose and the remaining content is organized under Cost/Inputs/Returns/Errors/Next headers, which is easy to scan. The 'Returns' bullet, however, is a very long dense run-on enumerating every notice type, which slightly hurts conciseness even though the detail is justified by the absence of an output 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, so the description must explain return values and it does so exhaustively (tier, scheduledTier, period/grace bounds, state enum, units, credit, limits, linkedBoxes, notices with per-type field breakdowns). Combined with the auth details, error codes, and follow-on tool routing, nothing needed to call this 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%, so the schema already documents 'address' (including 'any letter case') and the agentSignature object in depth. The description's 'Inputs' line only restates the address path parameter, adding no syntax or semantics beyond the schema, which is the baseline-3 case.

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?

The opening sentence states a specific verb ('Reads') and resource ('an account's tier, its period, the units used and left, and its limits'), enumerating the returned fields so an agent knows the scope. It does not, however, differentiate itself from plausible siblings like accountTier or accountUsage, which appear to expose subsets of the same data, so it falls short of a 5.

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?

Usage is well supported by the 'Next' section (tradeSearch to spend units, boxLink to link a box) and by error-based routing (404 account_not_found → 'Create one with accountCreate'). What is missing is explicit guidance on when to prefer this over accountTier/accountUsage, so it is clear context without exclusions.

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