Skip to main content
Glama

arcgate

by dev.arcgate
OverviewDiscussionsAdmin

accountUsage

Reads the units an account's draws took, by UTC day and by operation, in the current period and in the period the last renewal replaced.

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

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

  • Returns: accountId, current and previous, each periodStart, periodEnd, byDay (the UTC day as YYYY-MM-DD with its units, oldest first, a day with no draw absent) and byOperation (each operation with its units, most units first, then by name). An operation is the operationId of a keyed call (tradeSearch, tradeQuote, agentSearch, agentProfile, agentWallet) or, for a linked box's watch hit, the message type (watch.token, watch.screen, watch.agent). Draws paid from credit past the period's units are counted. A refunded draw is not. previous is null before the first renewal. A draw made in the grace after a period ended is counted in that period, even when a renewal in grace then started the next period at its periodEnd.

  • 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:

    • accountStatus: read the units left.

    • accountCredit: buy credit for the draws past the period's units.

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.5/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: cost is free, auth is either a signature over GET with no body (or an empty-bytes hash) or an ARCGATE-KEY, and it discloses subtle billing semantics — credit-paid draws counted, refunded draws not, grace-period draws attributed to the closed period, and previous being null before the first renewal.

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?

The opening sentence front-loads the purpose, then bold section headers (Cost, Inputs, Returns, Errors, Next) organize the detail. Given the absence of an output schema, the lengthy Returns section is justified rather than wasteful, and every sentence carries operative information.

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 two-parameter read tool with a nested auth object, no annotations, and no output schema, the description supplies everything an agent needs: purpose, auth modes, return shape, boundary cases, and error conditions with recovery paths (accountCreate for 404, key/account mismatch for 403).

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 address and agentSignature parameters are already fully documented in the schema. The description restates that address is a path param in any letter case but adds no syntax or constraint beyond the schema, making the baseline 3 appropriate.

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 verb (reads) and a precisely scoped resource: the units an account's draws took, broken out by UTC day and by operation, across the current and previous period. This distinguishes it cleanly from siblings like accountStatus (units left) and accountCredit (buying credit), which it explicitly names.

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 routes the agent to accountStatus for remaining units and accountCredit for purchasing past-period draws, and the Cost line clarifies this read draws nothing. It stops short of stating an explicit 'do not use this when...' exclusion, so it is clear context rather than full when/when-not guidance.

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