Skip to main content
Glama
Sign In

Polyrank

by io.github.polyrank
OverviewDiscussionsAdmin

Polyrank skill-rank movers

polyrank_get_movers
Read-onlyIdempotent

Traders whose skill rank climbed or fell the most recently (leaderboard momentum). Returns top climbers and fallers for a ranking preset over a lookback window.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows per direction (max 10, default 5).
presetNoRanking preset id (default "polyrank-default").
lookback_daysNoLookback window in days (max 30, default 7).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safe, idempotent, read-only profile, so the description only needs to add semantics. It does: results are split into two directions (climbers and fallers) and scoped by preset and lookback window, which tells the agent the response is bidirectional and time-bounded rather than a plain list.

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?

Two short sentences, front-loaded with what the tool returns, then the scoping dimensions. No filler or restated field definitions.

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?

For a small read-only tool with three optional, fully documented params plus annotations and no output schema, the description covers purpose, output shape and scoping. Only the meaning of 'skill rank' and the ordering/tie-breaking of movers is left 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?

Schema description coverage is 100%, so limits, ranges and defaults are already documented. The description only adds that the limit is effectively per direction ('top climbers and fallers') and that preset/lookback shape the comparison, which is a marginal gain.

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+resource: traders whose skill rank climbed or fell most recently, with a concrete output shape (top climbers and fallers). The parenthetical 'leaderboard momentum' distinguishes it in spirit from a static leaderboard, though it never names the sibling directly.

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?

Implied usage is clear enough — you call this to spot momentum/rank movement rather than absolute rank. But there is no explicit when-to-use versus polyrank_get_leaderboard or polyrank_get_trader_skill, and no stated prerequisites or cost/rate context.

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