Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Signature verify, EIP-191: recover the signer of an Ethereum message

evm_verify_signature
Read-only

Verify an Ethereum personal_sign (EIP-191) signature: recover the address that signed a message and, given an expected address, say whether it matches. Works for ordinary wallets (EOAs); smart-contract wallets sign by ERC-1271, which this offline check does not cover. Use for sign-in-with-wallet, proving wallet ownership or checking a signed order. A malformed signature is 400, uncharged. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "message": "<message>",
      "signature": "<signature>"
    },
    "name": "evm_verify_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNotrue to treat a 0x message as raw bytes instead of text
addressNoOptional expected signer address to compare
messageYesThe exact message that was signed (or 0x hex with raw=true)
signatureYes0x signature, 65 bytes (130 hex characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the check is offline, that malformed signatures return 400 and are uncharged, the pricing model ($0.01/call via x402 or credits, first 25 free, failed calls free), and explains why repeats cost money. The line 'reads or computes only and changes nothing' echoes readOnlyHint, but the cost and error behavior add real value that structured fields do not carry.

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-loads the core operation and the ERC-1271 limitation, then adds cost and safety notes. It is dense but nearly every clause carries information; the pricing sentence is the longest and only tangentially relevant to invocation correctness.

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 no output schema, the description still conveys what comes back (a recovered address and a match verdict), the error path, the cost implications, and the key limitation. Nothing material is missing for an agent deciding whether and how to call this.

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

Parameters3/5

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

Schema coverage is 100%, so all four parameters are already documented, including the optional expected address and the raw flag. The description reinforces the address-comparison behavior but adds nothing about the raw/hex-message option or signature format beyond what the schema states, so this sits at the baseline.

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?

States a specific verb and resource (verify an EIP-191 personal_sign signature, recover the signer address, optionally compare to an expected address). The scope is narrow enough to distinguish it from sibling verification/extraction tools like merkle_verify or evm_checksum.

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?

Gives concrete use cases (sign-in-with-wallet, proving wallet ownership, checking a signed order) and an explicit exclusion: ERC-1271 smart-contract wallet signatures are not covered by this offline check. It does not name an alternative tool to use for that excluded case, which keeps it short of a 5.

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.