Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_decode_tx

Decode EVM calldata and live transactions to identify contract calls and flag unlimited ERC-20/NFT approvals before signing.

Instructions

Paid x402 API ($0.005 USDC on Base): EVM calldata & live transaction decoder via OpenChain + EVM RPC; flags unlimited ERC-20/NFT approvals before signing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verifystack_decode_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional target contract address
dataNoRaw 0x hex calldata to decode
chainNo
txHashNoOptional live 0x tx hash to fetch and decode
valueWeiNoOptional native value in wei

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavioral context: the tool is paid ($0.005 USDC on Base) and combines OpenChain with live EVM RPC. What it omits is significant for a 5-parameter tool with zero required parameters — it never says what happens if neither `data` nor `txHash` is supplied, nor what the response contains.

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?

A single dense sentence that front-loads the pricing and payment chain before the capability, so an agent sees the cost constraint immediately. Nothing is redundant, though the semicolon-joined clauses make it slightly hard to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with five all-optional parameters and no output schema, the description should clarify which inputs are mutually substitutable and roughly what comes back (decoded calls, approval warnings). It conveys the capability and cost but leaves input-selection and output shape to inference.

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 80%, so the schema already documents most parameters and the baseline is 3. The description adds meaningful framing by characterizing the two distinct input modes (raw calldata decoding vs. live transaction fetch-and-decode), which helps an agent understand the purpose of `data` vs. `txHash` beyond their one-line schema text.

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 names a specific verb and resource ('EVM calldata & live transaction decoder') and lists the underlying sources (OpenChain + EVM RPC), which is enough for an agent to distinguish it from siblings like verifystack_token_safety or verifystack_verify_signature. It stops short of explicitly naming an alternative it should be preferred over.

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?

'Flags unlimited ERC-20/NFT approvals before signing' implies a pre-transaction safety check, which gives some context for when to call it. However, there is no explicit when-to-use vs. when-not guidance and no mention of how this relates to the other verification/safety tools in the catalog.

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