AgentIndex x402

Wallet Intelligence

wallet_intelligence

Read-onlyIdempotent

One call replaces wallet-balance and gas reads across Base, Ethereum, Polygon, Arbitrum and Optimism. Returns native and USDC balances, current blocks, fees and Base x402 payment readiness. One signature instead of ten paid requests. Try GET /wallet-intelligence/sample.

Input Schema

TableJSON Schema

Name	Required	Description
`address`	Yes	EVM wallet address to inspect across all selected networks.
`networks`	No	Up to five networks; defaults to all supported EVM networks.
`amount_usdc`	No	Amount to compare with the Base USDC balance for x402 readiness.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`errors`	Yes
`address`	Yes
`networks`	Yes
`x402_receipt`	No
`x402_readiness`	No
`requested_networks`	Yes
`rpc_reads_replaced`	Yes
`successful_networks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 27, 2026

addedInput schema / properties / address / description

Added value: +"EVM wallet address to inspect across all selected networks."

addedInput schema / properties / amount_usdc / description

Added value: +"Amount to compare with the Base USDC balance for x402 readiness."

addedInput schema / properties / networks / description

Added value: +"Up to five networks; defaults to all supported EVM networks."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "errors": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "networks": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "requested_networks": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "rpc_reads_replaced": {
+      "type": "integer"
+    },
+    "successful_networks": {
+      "type": "integer"
+    },
+    "x402_readiness": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "x402_receipt": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "address",
+    "requested_networks",
+    "successful_networks",
+    "rpc_reads_replaced",
+    "networks",
+    "errors"
+  ],
+  "type": "object"
+}

AddedSep 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld. The description adds real value beyond them by disclosing the cost/payment model ("One signature instead of ten paid requests") and the aggregation scope across chains, which is not derivable from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the consolidation value, then the return payload, then the cost model and a sample endpoint. No filler sentences; every line earns its place.

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?

An output schema exists, so return-value documentation is not required, yet the description still summarizes the payload shape usefully. Coverage of auth/payment prerequisites (what the "one signature" requires) is hinted at but not fully spelled out, keeping it just under complete.

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 100%, so the baseline is 3. The description still adds meaning by naming the five networks that the optional networks param defaults to and by tying amount_usdc to "x402 payment readiness," clarifying the comparison the parameter drives.

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 action (a single consolidated read) and enumerates exactly what is returned: native and USDC balances, current blocks, fees, and Base x402 payment readiness, across five named chains. This distinguishes it from the wallet_balance and gas_price siblings without the agent needing to open schemas.

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?

"One call replaces wallet-balance and gas reads" and "One signature instead of ten paid requests" clearly signal when to prefer this over the narrower siblings. It lacks an explicit when-not/exclusion (e.g., when single-chain reads are cheaper), so it stops short of a full 5.

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

All AgentIndex x402 tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.