Skip to main content
Glama

arcgate

by dev.arcgate
OverviewDiscussionsAdmin

keyRevoke

Deletes a key. It is a 401 key_invalid from the next call, over HTTP and MCP. Every box the key linked is unlinked with it, each with a fresh allowance (boxUnlink).

  • Cost: Free. Signed by the owner over method DELETE, path /account/v1/<address lowercased>/key/<id> 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 and id (path). No body.

  • Returns: revoked and the id. The account and its other keys are untouched, and so are the boxes its other keys and its owner linked.

  • Errors:

    • 404 account_not_found: the address has no account.

    • 404 key_not_found: the account has no key with that id. It was never made, was already revoked, or is another account's.

  • Next:

    • keyCreate: make another key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesA key's id, `key_` and 22 base64url characters, as `keyCreate` and `keyList` answer it. It is not the 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.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 delivers: it discloses that the key is permanently invalidated, that all linked boxes are unlinked with fresh allowances, that the operation is free, that it requires an owner EIP-712 signature (not just the ARCGATE-KEY header), and it enumerates specific error cases. This is thorough behavioral disclosure.

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 description is front-loaded with purpose and structured with clear bullet points for cost, inputs, returns, errors, and next steps. Despite its length, every section adds necessary information for a complex operation, with no wasted sentences.

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?

Given the complexity of a signed deletion with side effects, no annotations, and no output schema, the description provides everything an agent needs: what happens to the key and boxes, authentication requirements, exact signing payload, error conditions, and follow-up actions. Nothing critical 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, but the description adds meaningful context beyond the schema: it states that address and id are path parameters and that there is no request body, and it specifies the exact method (DELETE) and path pattern needed for the agentSignature, which is critical for correctly constructing the signature parameter.

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 description opens with 'Deletes a key' – a specific verb and resource – and immediately clarifies the consequence (401 key_invalid from the next call) and side effect (linked boxes unlinked). This distinguishes it from keyCreate, keyList, and keyRotate without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'Deletes a key', and a follow-up is suggested ('keyCreate: make another key'), but there is no explicit guidance on when to use this versus keyRotate (which likely replaces a key) or other alternatives. An agent must infer the use case from the name and description alone.

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