Skip to main content
Glama
Sign In

Vike Data API

by io.vike
OverviewDiscussionsAdmin

Wallet PnL History

wallet_pnl_history
Read-onlyIdempotent

Daily net-flow series for a wallet over the last N days (proxy for daily PnL). Returns per-day net inflow USD + cumulative + gross volume + tx count. NOTE: this is net inflow USD, not true realized PnL (which would require WAC accounting per token). Useful as a directional indicator.

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

Input Schema

NameRequiredDescriptionDefault
daysNoDays back (default 30, max 365)
chainNoChain (default ethereum)ethereum
addressYesWallet address (0x-prefixed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent and non-destructive, so safety needs no restating. The description adds the non-obvious caveat that the series is net inflow USD rather than realized PnL requiring WAC accounting — exactly the kind of context that prevents a downstream agent from mislabeling the output. It does not discuss rate limits or data latency.

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?

Three short sentences, front-loaded with purpose, then return fields, then the caveat. Every clause carries information, though the NOTE plus the 'directional indicator' sentence slightly overlap in hedging the metric's reliability.

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?

With no output schema, the description correctly compensates by enumerating the returned fields (net inflow USD, cumulative, gross volume, tx count). Combined with annotations covering the safety profile and a fully described 3-parameter schema, an agent has enough to call it correctly; only data freshness/latency is unaddressed.

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%, including defaults, enum values and the 365-day cap, so the schema carries parameter meaning fully. The description only echoes the 'last N days' window and adds nothing about chain selection or address format. Baseline 3 is appropriate.

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 resource and shape: a daily net-flow series for a wallet over N days, with the exact per-day fields returned. It also distinguishes itself conceptually from a true PnL tool by calling itself a proxy. It doesn't name any sibling (e.g. wallet_summary) as the alternative, so it stops 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 Guidelines3/5

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

"Useful as a directional indicator" implies the appropriate use case (rough trend reading, not accounting), which is genuine guidance. However, there is no explicit when-not condition and no named alternative for agents that need true realized PnL or per-token cost basis.

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