Skip to main content
Glama

EIP-712 signature request inspector (permits, x402)

chain_sign_inspect
Read-only

Inspects EIP-712 typed data before signing: kind (EIP-2612 or DAI permit, Permit2 allowance or transfer, EIP-3009 transfer authorization as used by x402, Seaport order, Safe transaction, generic), digest, chain id with mismatch check, verifying contract with token symbol and decimals, spender or recipient, raw and formatted amount, unlimited flag, deadline window in ISO time, risk level, flags with reasons, one-line summary. Sources: JSON-RPC via PublicNode, Sourcify. Price: $0.002 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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": {
      "typed": "<typed>"
    },
    "name": "chain_sign_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
typedYesEIP-712 typed data as JSON (URL-encoded in the query) or base64 of it, max 16 KB; also accepts eth_signTypedData_v4 params [address, typedData].
expected_chainNoChain the signature should be for (id such as 8453 or eip155:8453, or a supported name); a different domain chainId is flagged.
expected_spenderNoAddress expected as spender or recipient (the payTo for an x402 payment); a different address is flagged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description adds crucial behavioral context beyond the annotations, particularly around cost and reliability. It discloses the pricing model ($0.002 per successful call) and specific charging rules, which significantly informs operational behavior and reliability expectations.

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 definition is highly dense and front-loaded with information. While it could be segmented into bullet points for better readability, the single descriptive paragraph is incredibly efficient at conveying technical complexity and functional scope.

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 complex nature of blockchain standards, the tool is highly complete. It details the specific types of data checked, operational costs, risk assessment inclusion, and the validation logic required for an agent to use it correctly and safely.

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?

Although schema coverage is 100%, the description clarifies the functional meaning behind the parameters. It explains what types of data the 'typed' input accepts (e.g., EIP-2612, DAI permit) and the importance of the 'expected_spender' address.

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 clearly defines the tool's purpose: inspecting EIP-712 typed data before signing. It specifies a rich set of validation tasks, including checking digests, chain IDs, and contract verification against token symbols.

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?

While the description doesn't explicitly name competitors or use cases, it provides a very clear conceptual boundary by defining its role as a pre-signing inspection tool. The usage is inherently specific to complex EIP standards mentioned.

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