Skip to main content
Glama
Sign In

Polyrank

by io.github.polyrank
OverviewDiscussionsAdmin

Polyrank trader skill profile

polyrank_get_trader_skill
Read-onlyIdempotent

A single Polymarket wallet’s skill profile: composite rank, P&L, win-rate, volume, trades/markets, and commodity percentiles. The deep skill grid — full Brier decomposition, alpha-vs-mid, information coefficient, Sharpe, copyability & max copyable clip, true slippage, realized volatility, the hold-time split, peak/avg capital-at-risk, copier-realized return, and the copy verdict — is gated to the paid x402 agent tier (/v1/agent/*).

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

Input Schema

NameRequiredDescriptionDefault
addressYesProxy wallet address (0x + 40 hex).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 adds one genuinely useful behavioral fact: the deep skill grid (Brier decomposition, alpha, IC, Sharpe, etc.) is gated to the paid x402 agent tier. It still omits auth mechanics, rate limits, and what the free-tier response actually returns when the gated fields are absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first clause, which is good. But the long enumeration of gated deep-grid metrics is a comma-spliced list of a dozen items that adds bulk without helping an agent decide or invoke the tool, making the sentence harder to scan than it needs to be.

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?

There is no output schema, so the description must describe return content, and it does — listing both free-tier fields and the paid deep grid, plus the gating mechanism. For a single-parameter read tool this is close to complete; only the exact free-tier response shape when gated remains unstated.

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?

With one parameter and 100% schema description coverage ('Proxy wallet address (0x + 40 hex)'), the schema already carries the parameter meaning. The description adds no address format, validation, or edge-case detail, so 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 concrete resource (a single Polymarket wallet's skill profile) and enumerates what the profile contains: composite rank, P&L, win-rate, volume, trades/markets, percentiles. The word 'single' implicitly separates it from polyrank_get_traders_batch and polyrank_rank_wallets, but no sibling is named explicitly.

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 is implied — you call this to inspect one wallet's skill/performance — and the paid-tier gating note hints at a tier constraint. However, there is no explicit when-to-use vs alternatives (e.g. batch lookup, leaderboard, calibration) and no stated prerequisites beyond the gating aside.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Polyrank 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