Skip to main content
Glama

arcgate

by dev.arcgate
OverviewDiscussionsAdmin

keyList

Lists the account's keys by id, label, creation time and last use. A secret is never listed.

  • Cost: Free. Signed by the owner over method GET, path /account/v1/<address lowercased>/key/list and no body (the hash of no bytes). 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.

  • Returns: keys, oldest first, each with id, label, createdAt and lastUsedAt, which is null for a key never used. The first key accountCreate returned is labeled first key.

  • Errors:

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

  • Next:

    • keyRotate: replace a key's secret.

    • keyRevoke: delete a key.

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.6/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 the call is free, names the exact signing contract (method, path with lowercased address, empty body hash), states which credential does NOT work, and enumerates the failure modes (401 signature_required, 404 account_not_found). That is far more behavioral context than a typical read tool provides.

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?

Bulleted sections (Cost/Inputs/Returns/Errors/Next) are front-loaded with the purpose and scannable. There is mild duplication of the signing contract between the top-level description and the agentSignature property description, but each block still carries distinct operational value.

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 correctly compensates by describing the return payload ('keys, oldest first', with id/label/createdAt/lastUsedAt and null-for-unused semantics). Combined with error enumeration and signing details, an agent has everything needed to invoke and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by specifying that `address` is accepted in any letter case and, more importantly, that the request `path` must use the lowercased address — a signing requirement not derivable from the schema alone.

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 opening sentence gives a specific verb and resource ('Lists the account's keys') plus the exact fields returned, and immediately adds a scope constraint ('A secret is never listed') that an agent needs. It is trivially distinguishable from keyCreate/keyRotate/keyRevoke siblings without opening any 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 the agent to keyRotate and keyRevoke, and the 404 bullet routes it to accountCreate. The Cost bullet also states the auth condition explicitly ('ARCGATE-KEY does not authorize it: a call with only a key is a 401 signature_required'). It stops short of a general when-to-use/when-not statement, but the alternative routing is unusually concrete.

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