Skip to main content
Glama
polyrank

PolyRank MCP

Official
by polyrank

Polyrank live pulse

polyrank_get_pulse
Read-only

Track live Polymarket activity including realized profits, sharp-money moves, top trades, and trending markets. Identify where smart money is moving and consensus divergences.

Instructions

Live Polymarket activity: big wins just banked (realized profit), sharp-money moves, the biggest recent trades, trending markets by volume, and markets where Polyrank consensus diverges most from the market mid. Good for "what is smart money doing right now".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description adds context beyond annotations: it discloses that the tool returns live data on 'big wins just banked (realized profit), sharp-money moves, the biggest recent trades, trending markets by volume, and markets where Polyrank consensus diverges'. This aligns with readOnlyHint and openWorldHint. No contradiction.

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?

The description is a single concise paragraph with no wasted words. Key information is front-loaded, and every sentence adds value. It efficiently conveys the tool's purpose and output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite lacking an output schema, the description enumerates the types of data returned (big wins, sharp-money moves, etc.), providing sufficient context for an agent to understand what the tool provides. For a zero-parameter snapshot tool, this is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and schema description coverage is 100%. The description does not need to add any parameter semantics; it appropriately describes the output content.

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 clearly states the tool provides live Polymarket activity including big wins, sharp-money moves, largest trades, trending markets, and consensus divergence. The phrase 'what is smart money doing right now' succinctly captures its purpose and distinguishes it from sibling tools like leaderboard or trader-specific reports.

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?

The description explicitly recommends the tool for the query 'what is smart money doing right now', providing a clear use case. However, there is no explicit guidance on when not to use it or mention of alternative tools, but the context signals and sibling names imply appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/polyrank/PolyRank-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server