Skip to main content
Glama
Sign In

Vike Data API

by io.vike
OverviewDiscussionsAdmin

Predict.fun Wallet Flows

predictfun_wallet_flows
Read-onlyIdempotent

Where one Predict.fun wallet's money came from and went: its USDT deposits (in) and withdrawals (out) on BNB Chain, newest first, each with the counterparty address and our label for it, such as cex/binance; transfers with Predict.fun's own contracts (trading, splits, merges, redemptions) are left out. Returns {flows, totals, next_cursor, as_of_ts}; totals cover the whole history since 2025-11-21: deposited, withdrawn, net, and the first deposit with its sender (first_funder). It is the wallet's whole USDT traffic outside Predict.fun (a wallet also used elsewhere carries that activity too); dust under one cent and per-transaction fees are left out.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows (default 100, max 10000).
cursorNoA previous page's `next_cursor`, unchanged, to read the next page.
addressYesThe wallet, 0x and 40 hex digits. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context on top: internal contract transfers are filtered out, dust under one cent and per-transaction fees are excluded, totals span the whole history since 2025-11-21, and `first_funder` returns the first deposit's sender. It also discloses the response envelope, which is not covered by any output schema.

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 dense paragraph that front-loads the core definition (source and destination of a wallet's USDT) before qualifications and exclusions. The parenthetical and trailing caveats are useful but make it slightly heavy for a read-only lookup; minimal trimming would improve it.

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 carries the full burden of explaining returns and does so thoroughly: `{flows, totals, next_cursor, as_of_ts}` plus the totals breakdown (deposited, withdrawn, net, first_funder) and the as-of coverage date. Nothing an agent needs to interpret results or paginate is 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%, so limit, cursor, and address are already documented in the schema. The description reinforces the `address` semantics (a Predict.fun wallet) and mentions `next_cursor` only in the context of the return payload, adding no new syntax or format detail beyond structured fields. Baseline 3 applies.

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 precise verb+resource+scope: a Predict.fun wallet's USDT deposits (`in`) and withdrawals (`out`) on BNB Chain with counterparty labels. It also names what is deliberately excluded (transfers with Predict.fun's own contracts such as trading, splits, merges, redemptions), which separates it from the sibling trades/positions tools without ambiguity.

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?

The description establishes clear context for use — the wallet's whole USDT traffic outside Predict.fun, newest first — and warns that a wallet used elsewhere will carry that outside activity too. It stops short of naming an explicit alternative for on-platform flows (e.g., the trades tool), so the agent must infer where to go for internal Predict.fun transfers.

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 toolsInspect
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