arcgate

boxStatus

Reads a box's allowance, unit balance, message counts and unstored watch hits.

Cost: Free. Signed by the box's agent over method GET, path /agent/v1/<address lowercased>/box/status and no body (the hash of no bytes). Or send an ARCGATE-KEY of the account the box is linked to, with no signature. Another account's key, or any key for a box that is not linked, does not apply to the box: the call is checked as if no key were sent, so it needs the signature. A key nobody holds is a 401 key_invalid. The key keeps working after the account has lapsed (its grace has ended).
Inputs: address (path).
Returns: allowance (messagesLeft, expiresAt, expired), unitBalance (the units a watch hit draws after the cutover, none left pauses the watches), linkedAccount (the account the box is linked to, or null: while its period or grace runs the box does not expire, see boxLink), maxUnitsPerDay (the box's daily spend cap in units, or null for none, see boxSpendCap), counts and unstoredWatchHits. registeredAgents lists the ERC-8004 agents the address owns or is the wallet of. It is information only.
Errors:
- 404 box_not_found: the address has no box. Create one first (boxCreate).
Next:
- boxTopUp: add messages and days.
- boxUnitsBuy: add units.
- boxSpendCap: cap the units its watch hits draw in a day.
- boxMessageList: read the box's messages.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`address`	Yes	The box's address: the agent's own address (an EOA or an EIP-7702 account), any letter case. The box is keyed by it, and a signed request must be signed by it.
`agentSignature`	No	The agent'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 `AgentRequest` with fields `address` (the box), `method`, `path`, `bodyHash`, `nonce` and `expiry`, under the domain {name: "arcgate", version: "1"} with no chainId (a wallet that can only sign with one, such as Circle's, may add the chainId of the chain this deployment serves, 5042 on Arc mainnet, and no other). The `path` is the request path with every parameter filled in and 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. Omitting it is a 401 signature_required unless an ARCGATE-KEY of the account the box is linked to is sent (over MCP, on the connection), and it is never a charge: the call is free.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / agentSignature / description

Previous value: -"The agent'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 `AgentRequest` with fields `address` (the box), `method`, `path`, `bodyHash`, `nonce` and `expiry`, under the domain {name: \"arcgate\", version: \"1\"} with no chainId (a wallet that can only sign with one, such as Circle's, may add the chainId of the chain this deployment serves, 5042 on Arc mainnet, and no other). The `path` is the request path with every parameter filled in and 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. Omitting it is a 401 signature_required, never a charge: the call is free."New value: +"The agent'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 `AgentRequest` with fields `address` (the box), `method`, `path`, `bodyHash`, `nonce` and `expiry`, under the domain {name: \"arcgate\", version: \"1\"} with no chainId (a wallet that can only sign with one, such as Circle's, may add the chainId of the chain this deployment serves, 5042 on Arc mainnet, and no other). The `path` is the request path with every parameter filled in and 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. Omitting it is a 401 signature_required unless an ARCGATE-KEY of the account the box is linked to is sent (over MCP, on the connection), and it is never a charge: the call is free."

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / agentSignature / description

Previous value: -"The agent'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 `AgentRequest` with fields `address` (the box), `method`, `path`, `bodyHash`, `nonce` and `expiry`, under the domain {name: \"arcgate\", version: \"1\"} with no chainId. The `path` is the request path with every parameter filled in and 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. Omitting it is a 401 signature_required, never a charge: the call is free."New value: +"The agent'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 `AgentRequest` with fields `address` (the box), `method`, `path`, `bodyHash`, `nonce` and `expiry`, under the domain {name: \"arcgate\", version: \"1\"} with no chainId (a wallet that can only sign with one, such as Circle's, may add the chainId of the chain this deployment serves, 5042 on Arc mainnet, and no other). The `path` is the request path with every parameter filled in and 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. Omitting it is a 401 signature_required, never a charge: the call is free."

AddedOct 7, 2026

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 richly: cost is free, the two auth paths (EIP-712 signature vs. ARCGATE-KEY of the linked account), the exact case where a key is ignored, the 401 key_invalid behavior, key validity after account lapse, and the 404 error. This is exceptional behavioral disclosure for a read tool.

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 headers (Cost/Inputs/Returns/Errors/Next) front-load the essentials and every bullet is substantive. It is dense and on the long side, but the auth detail is genuinely load-bearing given zero annotations, so little is wasted.

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?

No output schema exists, yet the description enumerates every returned field (allowance sub-fields, unitBalance, linkedAccount, maxUnitsPerDay, counts, unstoredWatchHits, registeredAgents) with meaning, and covers inputs, errors and follow-ups. Nothing an agent needs to call 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 nested agentSignature object is documented exhaustively in the schema, so the description need not add parameter detail. It only notes 'address (path)', which the schema already covers; baseline 3 applies when the schema does the heavy lifting.

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') plus the exact resource scope: a box's allowance, unit balance, message counts and unstored watch hits. An agent can distinguish it from accountStatus and boxMessageList without opening either schema.

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 to related operations (boxTopUp, boxUnitsBuy, boxSpendCap, boxMessageList) and the auth bullets make clear this is a free read. However, it never states when to prefer this over a sibling status tool or any exclusion condition, so usage is contextual rather than prescriptive.

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

All arcgate tools Inspect

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

Need Help?