ScorpTech x402 API

Evm Token Transfers

evm_token_transfers

Read-onlyIdempotent

Latest ERC-20 or ERC-721 Transfer events for a token contract (optionally filtered to one wallet, in/out/both) on six EVM chains. Adaptive eth_getLogs window with automatic shrink on provider range caps. Returns decoded from/to/value or tokenId, approx age, mint/burn tags. Read-only. Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/evm-token-transfers

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": {
      "token": "<token>"
    },
    "name": "evm_token_transfers"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Annotations already declare read-only/non-destructive, yet the description adds genuinely new behavioral facts: an adaptive eth_getLogs window that auto-shrinks on provider range caps, the decoded return fields including mint/burn tags, and a payment requirement ($0.01 USDC per successful call via x402 on Solana). Disclosing cost and the HTTPS alternative endpoint is exactly the kind of context annotations cannot convey.

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?

Five compact sentences with the core purpose front-loaded and operational/pricing details trailing, which is the right ordering. Slightly dense in the middle (eth_getLogs mechanics) but no sentence is wasted.

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

Completeness4/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 helpfully enumerates return fields (from/to/value or tokenId, approx age, mint/burn tags), and it discloses cost and chain coverage. The only real gap is the mismatch between mentioned wallet/direction filters and the actual one-parameter schema.

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 0% for the single 'token' parameter, so the description must carry the load; it does clarify that 'token' means a token contract address. However, it advertises '(optionally filtered to one wallet, in/out/both)' when the schema exposes only 'token', creating ambiguity about parameters that do not exist in the input schema.

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?

States a specific verb and resource ('Latest ERC-20 or ERC-721 Transfer events for a token contract') plus scope (six EVM chains), which is far more precise than the title alone. It does not explicitly differentiate itself from nearby siblings like evm_read, evm_tx_info, or nft_metadata, so it stops short of a 5.

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?

The word 'Latest' and the event-type scoping imply when this tool applies, but there is no explicit 'use this when... instead of X' guidance and no stated exclusions or prerequisites. An agent can infer usage but must guess against alternatives such as evm_tx_info.

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

All ScorpTech x402 API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?