xportalx

nansen_wallet_profiler

Comprehensive wallet analysis. Supports natural language like 'profile vitalik.eth' or 'what labels does 0x... have?'. Returns balances, Nansen labels, and transactions. Cost: 0.01 USDC

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": "nansen_wallet_profiler"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Single chain (alternative)	ethereum
`input`	No	Natural language query (e.g., 'profile this wallet 0x...', 'analyze vitalik.eth')
`query`	No	Natural language query (alternative)
`chains`	No	Chains to query for balances/transactions
`wallet`	No	Wallet address (alternative)
`address`	No	Wallet address (0x...) or ENS name to analyze
`includeTransactions`	No	Include recent transactions (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedJan 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the cost (0.01 USDC) and the nature of the operation (returns data, no mention of mutation). However, it does not state whether the tool is read-only, any prerequisites, or error behavior, leaving gaps in behavioral disclosure.

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?

The description is three sentences, front-loaded with the core purpose. Each sentence provides distinct information: purpose, usage examples, return types, and cost. No wasted words.

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?

The description explains the return values (balances, labels, transactions) which is necessary since there's no output schema. It also covers the natural language capability. However, with 7 optional parameters, it doesn't clarify which parameter to prefer or how the tool behaves when multiple are provided, so it's not fully complete.

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 the baseline is 3. The description adds usage examples for natural language queries ('profile vitalik.eth') that clarify how to use the input/query parameters but does not add significant new semantics beyond the 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?

The description states 'Comprehensive wallet analysis' and gives concrete examples of queries and return types (balances, Nansen labels, transactions). It clearly indicates the tool profiles wallets, distinguishing it from sibling tools like get_wallet_balance by offering a broader scope. However, it does not explicitly name alternatives, so it's not a full 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 description implies the tool is for comprehensive profiling via the word 'comprehensive' and the list of return types, but it does not explicitly state when to use this tool versus simpler alternatives like get_wallet_balance. There is no 'use X instead' guidance, making usage context implied rather than explicit.

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

All xportalx 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?