Skip to main content
Glama
Sign In

Polyrank

by io.github.polyrank
OverviewDiscussionsAdmin

Polyrank highest-ROI resolved trades

polyrank_get_top_roi_trades
Read-onlyIdempotent

The biggest return-on-cost RESOLVED Polymarket bets (won positions with a real cost floor) — a hall-of-fame of single trades by ROI multiple. Optionally filter by market category (e.g. "Sports", "Politics", "Crypto"). Identities are masked (pseudonym only).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "polyrank_get_top_roi_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoSort direction (default "desc").
sortNoSort key (default "roi").
limitNoRows to return (max 100, default 50).
categoryNoMarket category filter, e.g. "Sports", "Politics", "Crypto".
since_daysNoOnly trades resolved within the last N days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly/idempotent/non-destructive, so the safety bar is met elsewhere. The description adds genuinely non-obvious behavioral context: only RESOLVED winning positions with a real cost floor are eligible, and identities are masked to a pseudonym — both material to interpreting results. It stops short of noting that sorting can surface non-ROI orderings.

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

Conciseness5/5

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

Three sentences, front-loaded with the core definition, then filter option, then privacy note. Every clause — cost floor, won positions, pseudonymized identities — delivers information an agent would otherwise have to guess.

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 all five parameters optional, annotations covering the safety profile, and no output schema, the description supplies enough scope context to call the tool correctly. The one omission is that the sort parameter permits profit/cost/entry/recency orderings, which the description's ROI-only framing does not foreshadow.

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 enums and defaults documented for dir, sort, limit, and since_days, so the schema carries the parameter burden. The description reinforces only the category filter and the ROI concept, adding little beyond what the schema already states.

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?

The description names a specific verb and resource — the highest return-on-cost resolved bets — and qualifies it precisely (resolved, won positions with a real cost floor, single trades ranked by ROI multiple). That framing separates it from the wallet-level siblings (polyrank_rank_wallets, polyrank_get_leaderboard, polyrank_get_traders_batch) without needing to name them.

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 only implied: the description notes an optional category filter, which signals "browse or narrow by sector," but it never states when to pick this over the leaderboard or ranking-template tools, and gives no exclusions. An agent must infer the choice from the phrase "hall-of-fame of single trades."

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