Skip to main content
Glama
fzlzjerry

polymarket-mcp

by fzlzjerry

polymarket_trending_markets

Read-only

Find active prediction markets sorted by 24-hour trading volume to identify trending topics.

Instructions

What's hot right now: active, open markets sorted by 24h volume (descending).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds that results are sorted by 24h volume and are active/open, which is useful but does not go beyond the annotations' safety profile.

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 sentence that front-loads the purpose with 'What's hot right now,' containing no extraneous information.

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

Completeness3/5

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

Given the simple input schema and existing output schema, the description provides the core behavior but lacks details on pagination, maximum limit, or how results relate to other tools.

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

Parameters2/5

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

The only parameter 'limit' has a default of 10 but is not mentioned or explained in the description; schema coverage is 0%, so the description misses the chance to clarify how limit affects results.

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 returns active, open markets sorted by 24h volume descending using the phrase 'What's hot right now,' effectively distinguishing it from sibling tools like polymarket_list_markets.

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?

The description implies usage for trending markets but does not explicitly state when to use this tool versus alternatives like polymarket_list_markets or polymarket_search, nor provides any exclusion criteria.

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/fzlzjerry/polymarket-mcp'

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