Skip to main content
Glama
Sign In

Vike Data API

by io.vike
OverviewDiscussionsAdmin

Predict.fun Wallet Positions

predictfun_wallet_positions
Read-onlyIdempotent

One wallet's Predict.fun positions and P&L, per outcome token: net shares, cost, proceeds, mark (last price), value (net x 1 won, x 0 lost, x mark while open), pnl = proceeds - cost + value, state (open, won, lost, uncatalogued); totals over ALL positions with realized (resolved) and unrealized (open) P&L. At most 500 positions are listed (open first, then the largest |pnl|): positions_total counts them all, truncated says some were left out. Exchange fills only: shares split, merged, redeemed or transferred are not seen.

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

Input Schema

NameRequiredDescriptionDefault
addressYesThe wallet, 0x and 40 hex digits. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing data-coverage limits: split, merged, redeemed and transferred shares are invisible because only exchange fills are read. It also quantifies output behavior: at most 500 positions, open first then largest |pnl|, with positions_total and truncated signaling omissions.

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?

Dense but front-loaded: identity and P&L definition come first, then truncation behavior, then the data-source caveat. The semicolon-chained formulas are efficient though slightly hard to parse in one pass; no sentence is filler.

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 return values, and it does: field meanings, pnl formula, state enumeration, totals for realized and unrealized P&L, truncation flags. Nothing an agent needs to interpret or trust the result 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?

The single address parameter is fully documented in the schema (0x plus 40 hex digits, required), so the description adds little parameter meaning beyond the phrase 'one wallet's', which confirms a single address rather than a batch. Baseline 3 is appropriate when schema coverage is 100%.

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?

States a specific verb-plus-resource: one wallet's Predict.fun positions and P&L, broken down per outcome token with enumerated computed fields. Scope is precise enough that an agent can distinguish it from a flows or trades tool, but no sibling is named explicitly, so it stops short of full differentiation.

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?

Usage context is implied by the scope statement (positions and P&L for a single wallet) and by the 'Exchange fills only' caveat, which tells the agent when the data will be incomplete. However, there is no explicit 'use this instead of X when Y' guidance against the sibling wallet_positions, predictfun_wallet_trades, or predictfun_wallet_flows tools.

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