Skip to main content
Glama
Sign In

Vike Data API

by io.vike
OverviewDiscussionsAdmin

Polymarket Wallet

polymarket_wallet
Read-onlyIdempotent

Profile a Polymarket trader: realized P&L (24h / 7d / 30d / all-time), hit-rate on resolved markets, total volume, top categories traded, and recent positions. Use when the user gives a Polymarket wallet address. Also returns correlated: up to 8 other wallets that trade the same markets (each sharing at least 3 markets and $500 of volume with this one, compared over its 1,000 largest markets), most shared markets first, each with proxy_wallet, pseudonym, display_name, shared_markets, overlap_volume_usd, overlap_trades and last_seen; [] = none qualifies. Same data as GET /v1/polymarket/wallets/{address} plus /wallets/{address}/correlated.

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

Input Schema

NameRequiredDescriptionDefault
windowNoWindow for windowed metrics (default all)all
addressYesPolymarket wallet address (0x-prefixed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description earns credit by disclosing the qualifying rule for `correlated` (min 3 shared markets and $500 overlap volume, scanned over the 1,000 largest markets, capped at 8, empty array when none) — behavioral detail no annotation could carry. It doesn't state caching, rate limits, or freshness, and the main profile block's return semantics are only named, not characterized.

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?

Front-loaded with purpose and metric list, then the API provenance, then the detailed `correlated` contract. Dense but every clause carries information; the correlated sentence packs many thresholds without filler, though it runs long and slightly buries the field list.

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?

No output schema exists, so the description must convey returns and it does so thoroughly for `correlated` (field-by-field). The primary profile payload is only listed as metric names with no types or units, which is a modest gap for a two-parameter read-only tool whose annotations are already complete.

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% with just two params, including an enum and a default, so the schema does the heavy lifting. The description's mention of '24h / 7d / 30d / all-time' loosely parallels the `window` enum but adds no syntax or format detail (e.g. whether 'all' is the default, which metrics are windowed vs. lifetime) beyond the schema. 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?

Opens with a specific verb+resource ('Profile a Polymarket trader') and enumerates exactly which metrics come back (realized P&L across four windows, hit-rate on resolved markets, volume, top categories, recent positions). That suite is distinguishable from siblings like polymarket_leaderboard or polymarket_smart_money without opening any schema.

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?

'Use when the user gives a Polymarket wallet address' gives a clear trigger condition. It stops short of naming when-not-to-use or routing to alternatives such as polymarket_leaderboard, hl_wallet, or wallet_summary, so it's clear context without exclusions.

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