Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_wallet_profile

Profile any EVM wallet across Base, Ethereum, Arbitrum, Optimism, and Polygon to inspect native/USDC balances, EOA vs contract status, nonce activity, and live gas fees before transacting.

Instructions

Paid x402 API ($0.008 USDC on Base): Multichain EVM wallet counterparty & gas profiler across Base, Ethereum, Arbitrum, Optimism, and Polygon (native/USDC balances, EOA vs contract check, nonce activity, live gas fees).

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": {
      "address": "<address>"
    },
    "name": "verifystack_wallet_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainsNoOptional list of chains (defaults to all 5)
addressYesEVM 0x address to inspect across chains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.6/5.0
Behavior4/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 discloses the most consequential trait an agent must know: this is a paid x402 endpoint costing $0.008 USDC on Base. It also enumerates the returned data categories and the chain coverage. It does not explain how payment is settled, whether calls can fail on insufficient balance, or rate limits, which keeps it from a 5.

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 sentence with the cost signal front-loaded ahead of the capability, which is the right ordering for a paid API. The parenthetical list is dense but every item earns its place by describing a distinct data category. Slight cost for being one long clause chain rather than clearly separated sentences.

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 two-parameter read tool with no output schema, the description does reasonably well by naming the data categories returned, substituting for an absent return-value spec. However, it leaves the payment mechanics, the response format, and per-chain failure behavior unexplained, which matters for a paid multichain call.

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 description coverage is 100%, so both parameters are already documented, including the 'defaults to all 5' behavior for chains and the 'EVM 0x address' semantics for address. The description adds nothing beyond restating the five chain names that appear as the schema enum. Baseline 3 applies when the schema does the work.

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 concrete resource and scope: a multichain EVM wallet 'counterparty & gas profiler' covering five named chains. The parenthetical enumerates exactly what is profiled (native/USDC balances, EOA vs contract, nonce activity, gas fees), so an agent knows what it gets. It stops short of naming a sibling it differs from, but the subject matter is distinct enough from the other verifystack tools.

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?

Usage is only implied by the subject: call it when you need wallet-level balance, contract-status, nonce or gas data on the listed chains. There is no explicit when-to-use/when-not statement, no pointer to an alternative sibling, and no note on when a single-chain call would be preferable to the default all-five-chains behavior.

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