Skip to main content
Glama

arcgate

by dev.arcgate
OverviewDiscussionsAdmin

keyCreate

Makes another key for the account, with a label. The key is shown once.

  • Cost: Free. Signed by the owner over method POST, path /account/v1/<address lowercased>/key and the body {"label": ...}. 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, and label (body), 1 to 64 characters.

  • Returns: the key's id and label, the key itself, shown only now, and createdAt. Send the key in ARCGATE-KEY.

  • Errors:

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

  • Next:

    • keyList: read the account's keys.

    • tradeSearch: pay for a search with the key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesA name for the key, 1 to 64 characters, to tell the keys apart in `keyList`. Not a secret.
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.3/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: cost (free), the exact signing scheme (typed data fields, domain, origin binding), the one-time visibility of the returned secret, and the concrete failure mode (404 account_not_found with the fix, accountCreate). It also notes the key is never charged on a missing signature.

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?

Front-loaded with the one-line purpose, then bolded sections (Cost, Inputs, Returns, Errors, Next) that let an agent skip what it does not need. The signature paragraph is dense and long, but given zero annotations that detail is load-bearing rather than padding.

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, so the description supplies the return shape (id, label, key, createdAt) itself. Combined with cost, auth, error and next-step coverage for a 3-param nested-object tool, 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.

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 goes beyond it by specifying that address is case-insensitive and that the signed path must have the address lowercased, plus the canonical-JSON bodyHash rule. That materially clarifies how agentSignature must be constructed, which the schema only gestures at.

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?

Opens with a specific verb+resource ('Makes another key for the account') plus a critical behavioral fact ('The key is shown once'). It is clearly distinguishable from keyList/keyRevoke by the 'Next' pointers, but it never explicitly contrasts itself with keyRotate, the nearest sibling that also produces a key.

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?

States the selection condition crisply: this is authorized only by an owner signature and explicitly NOT by the ARCGATE-KEY header ('a call with only a key is a 401 signature_required'). The 'Next' section routes to keyList and tradeSearch. It stops short of saying when to prefer this over keyRotate, which is the one sibling an agent could confuse it with.

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