Vike Data API

Wallet Transactions

wallet_transactions

Read-onlyIdempotent

Raw per-wallet transfer list (single transactions, not aggregates). Filter by direction (in/out/all), days back, min USD, and optionally a specific token and, for that token, an amount range in whole tokens. Returns time, tx_hash, from, to, token_address, symbol, amount (whole tokens; null when the token's decimals are unknown), value_usd, direction, block. Use when the user asks 'show me recent transfers for X' / 'last 100 transactions of wallet Y' / forensic audit queries.

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_transactions"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Days back (default 30, max 365)
`chain`	No	Chain (default ethereum)	ethereum
`limit`	No	Max transactions (default 50, max 500)
`address`	Yes	Wallet address (0x-prefixed)
`min_usd`	No	Filter dust below this USD value (default 0)
`direction`	No	Transfer direction (default all)	all
`max_amount`	No	Only transfers of at most this many tokens (whole tokens, not raw units, up to 1e18). Needs token_address (an amount across different tokens means nothing) and that token's decimals known, else an error. With min_usd, both must hold. Omit for no ceiling
`min_amount`	No	Only transfers of at least this many tokens (whole tokens, not raw units, up to 1e18). Needs token_address (an amount across different tokens means nothing) and that token's decimals known, else an error. With min_usd, both must hold. Omit for no floor
`token_address`	No	Optional: restrict to one token

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / max_amount

Added value: +{
+  "description": "Only transfers of at most this many tokens (whole tokens, not raw units, up to 1e18). Needs token_address (an amount across different tokens means nothing) and that token's decimals known, else an error. With min_usd, both must hold. Omit for no ceiling",
+  "type": [
+    "number",
+    "string"
+  ]
+}

addedInput schema / properties / min_amount

Added value: +{
+  "description": "Only transfers of at least this many tokens (whole tokens, not raw units, up to 1e18). Needs token_address (an amount across different tokens means nothing) and that token's decimals known, else an error. With min_usd, both must hold. Omit for no floor",
+  "type": [
+    "number",
+    "string"
+  ]
+}

First observedOct 25, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the returned field list and the null-amount caveat when token decimals are unknown. With annotations carrying the safety profile, this is adequate but not rich - no pagination/truncation behavior or rate-limit context.

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?

Two well-structured sentences with the core identity front-loaded and the usage examples trailing. The full return-field enumeration is long but earns its place given there is no output schema. Slight density cost but no wasted sentences.

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?

With no output schema, the description compensates by enumerating the return fields, including edge-case semantics (null amount when decimals unknown, amount in whole tokens). Parameter behavior is fully documented in the schema and the read-only safety profile in annotations, leaving nothing an agent needs missing.

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 100% and the schema already spells out the max_amount/min_amount dependency on token_address, whole-token units, and the decimals error condition. The description's filter summary ('direction (in/out/all), days back, min USD...') largely restates what the schema documents, adding little new meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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 a specific verb and resource ('raw per-wallet transfer list') and explicitly scopes it against aggregates ('single transactions, not aggregates'), which separates it from siblings like wallet_summary or wallet_pnl_history. It does not name the closest sibling (hl_wallet_trades or token_transfers) to disambiguate against those, so it falls 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 Guidelines4/5

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

It gives concrete when-to-use triggers, including quoted user phrasings ('show me recent transfers for X', 'last 100 transactions of wallet Y') and a forensic audit case, which is a clear context statement. It stops short of saying when NOT to use it or naming which sibling to pick instead of this one.

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.