Skip to main content
Glama

x420_verify_signature

Verify EIP-191 personal_sign signatures against Ethereum addresses or ed25519 signatures over canonical JSON against X420 agent public keys, returning validity and recovery details without network access.

Instructions

Signature verifier: Checks an EIP-191 personal_sign signature against an Ethereum address (pure recovery, EOAs only), or an ed25519 signature over canonical JSON against an X420 agent public key. No network. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.02 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: scheme, valid, recovered/public_key, reason, message_sha256 - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"scheme":"eip191","message":"x420 quote q_8f3a nonce 7c1d","address":"0xa1B2c3d4E5f60718293a4B5C6d7E8F9012345678","signature":"0x5d1b…(130 hex)…1c"}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "signature": "<signature>"
    },
    "name": "x420_verify_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemeNoeip191 (default) or ed25519
addressNoexpected 0x signer for eip191 (default: none)
messageNosigned text for eip191 (default: none)
payloadNosigned payload (JSON text or plain string) for ed25519 (default: none)
signatureYessignature hex
public_keyNoed25519 SPKI DER hex (88 chars) for ed25519 (default: none)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses the critical behavioral facts an agent cannot get from structured fields: the call is PAID at $0.02 USDC on Base via x402, drawn from the wallet in X420_MCP_WALLET_PRIVATE_KEY, and this is "real money" — explaining why readOnlyHint is false despite the operation being a pure computation. It also states there is no network access and enumerates the return payload (scheme, valid, recovered/public_key, reason, message_sha256) plus a signed receipt and settlement transaction.

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?

It is front-loaded correctly — purpose first, then constraints, then price, then return shape, then example — so an agent can decide early. The legal disclaimer sentence ("Not professional, legal, insurance...") consumes space without helping tool selection, and the example adds length, though both are arguably justified.

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?

With six parameters, no output schema, and a payment side effect, the description covers everything needed: supported schemes and their preconditions, cost and settlement wallet source, network-free operation, and the full return contract. An agent could invoke this correctly without inspecting anything else.

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 description coverage is already 100%, so baseline is 3, but the description adds real meaning: it ties scheme selection to which other fields matter (address/message for eip191, payload/public_key for ed25519) and provides a fully worked example input that shows the expected hex signature shape (130 hex chars, 0x prefix). It stops short of documenting the 88-character SPKI DER expectation for ed25519 in prose, which the schema still handles.

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 a precise verb+resource ("Signature verifier") and immediately names both supported schemes: EIP-191 personal_sign recovery against an Ethereum address, or ed25519 over canonical JSON against an X420 agent key. No sibling tool in the catalog verifies signatures, and the two modes are clearly delineated so an agent knows exactly which job this tool performs.

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?

It gives clear applicability constraints: "pure recovery, EOAs only" for eip191, "No network", and the eip191 default scheme versus ed25519 for agent keys. What it lacks is an explicit statement of when *not* to use it or a named alternative (e.g., for smart-contract wallets / EIP-1271, which are excluded by the EOAs-only caveat but not routed anywhere).

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