Vike Data API

Wallet Trace

wallet_trace

Read-onlyIdempotent

Trace a wallet's money through counterparties. direction=out follows where funds went, in where they came from, both (default) either way. At each hop, expand to the top N counterparties by USD volume in that direction. Returns nodes + edges of the resulting graph. Use when the user asks 'where did funds from X go' (out) / 'who funded Y' (in) / 'follow the money 3 hops from Z' / wallet investigation.

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

Input Schema

Name	Required	Description	Default
`chain`	No	Chain (default ethereum)	ethereum
`depth`	No	Hops to follow (1-5, default 2)
`width`	No	Top N counterparties per hop (1-10, default 5)
`window`	No	Window (default 30d)	30d
`address`	Yes	Root wallet to trace from
`min_usd`	No	Minimum USD per transfer to follow (default 10000)
`direction`	No	out = where funds went, in = where they came from, both = either (default both)	both

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A5/5.0

Behavior5/5

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

The description provides crucial behavioral details beyond the annotations, specifically stating that the tracing process expands 'to the top N counterparties by USD volume in that direction.' It also clearly defines the output as 'nodes + edges of the resulting graph.'

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 definition is highly efficient. Every sentence contributes directly to defining the scope, method, or application of the tool, with key information front-loaded.

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

Completeness5/5

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

Given the complexity of graph-based financial tracing (hops, volume, direction, window), the definition is comprehensive. It explains the input requirements and the structure of the resulting graph without omitting critical details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds vital semantic context, especially for parameters like `direction` (defining 'in' vs 'out') and `width` (defining the selection criteria as 'Top N counterparties by USD volume').

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?

The purpose is exceptionally clear: to 'Trace a wallet's money through counterparties.' It uses a specific verb and resource, clearly distinguishing itself from list-based or summary tools in the sibling ecosystem by focusing on graph traversal and financial flow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit natural language examples of when to use the tool, such as 'where did funds from X go' (out) or 'follow the money 3 hops from Z.' This comprehensive guidance eliminates ambiguity for the agent.

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

All Vike Data 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.