Skip to main content
Glama

arcgate

by dev.arcgate
OverviewDiscussionsAdmin

ownerTransfer

Proposes moving the account to another address. Nothing moves until that address accepts with ownerAccept. A second proposal replaces the first, which is how a mistyped address is fixed.

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

  • Inputs: address (path), the current owner, any letter case, and newOwner (body), the address to move the account to, any letter case.

  • Returns: accountId, owner, newOwner lowercased and expiresAt, the unix time the proposal lapses (account.transfer.days after now).

  • Errors:

    • 404 account_not_found: the address has no account.

    • 409 account_exists: newOwner owns an account already, this account included: an address owns at most one.

  • Next:

    • ownerAccept: the new owner signs it, at this account's path, to take the account.

    • accountStatus: read 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.
newOwnerYesThe address to move the account to, any letter case. It must own no account: an address owns at most one. A second proposal replaces the first.
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.7/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: it declares cost (free), that ARCGATE-KEY alone yields a 401 signature_required, the exact signing target (method/path/body), the expiry window via account.transfer.days, and the nonce-reuse rule. Specific failure codes (404 account_not_found, 409 account_exists) and the one-account-per-address invariant are disclosed up front.

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?

Front-loaded with the core behavior, then organized into Cost/Inputs/Returns/Errors/Next with bolded labels. The length is justified for a signing-required mutation with no annotations and no output schema; the only minor redundancy is the repeated 401 signature_required mention.

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 the description compensates by enumerating the return fields (accountId, owner, newOwner lowercased, expiresAt) and its semantics. Combined with errors, cost, and the follow-up tools, nothing an agent needs to call or interpret 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, newOwner and the nested agentSignature fields. The description's Inputs section largely restates that ('any letter case', 'the address to move the account to'), adding little beyond it. Baseline 3 is appropriate where 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?

The first sentence states a specific verb and resource ('Proposes moving the account to another address') and immediately scopes it ('Nothing moves until that address accepts with ownerAccept'). This distinguishes it from the sibling ownerAccept, which is the completing step rather than the proposing step. An agent can select it without opening the 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?

The two-phase workflow is explicit: this proposes, ownerAccept commits, and accountStatus reads. It also states the replacement rule ('a second proposal replaces the first, which is how a mistyped address is fixed'), giving the agent a clear condition for re-invoking rather than looking for an edit tool.

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