Skip to main content
Glama

X420 agent services

x420_verify_signature

Read-onlyIdempotent

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. Price: $0.02 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: scheme, valid, recovered/public_key, reason, message_sha256.

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 observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds critical operational context: the hosted tool validates input but returns payment instructions instead of the deliverable, the x402 retry flow, the local-server alternative, and the paid output fields. It also discloses the EOA-only and canonical-JSON constraints.

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?

The description is dense but front-loaded: purpose first, then constraints, payment behavior, and deliverable shape. The legal-advice disclaimer and repeated payment detail add some length, but the core information is well organized.

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?

For a payment-gated tool with no output schema, the description covers the verification semantics, the x402 payment handshake, the local-server alternative, and the deliverable fields. It gives an agent enough context to invoke the tool and understand what will happen.

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 schema already documents each parameter. The description adds meaning beyond the schema by specifying EIP-191 personal_sign pure recovery, EOA-only support, ed25519 over canonical JSON, and X420 agent public-key context.

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?

The description states a specific verb and resource: it verifies EIP-191 or ed25519 signatures and explains the relevant cryptographic contexts. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as hash_digest or evidence_timestamp.

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 explains the two signature schemes and the hosted-versus-local payment paths, so an agent knows how to obtain the paid result. It does not name sibling tools or state when a different verification or hashing tool would be preferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources