Skip to main content
Glama

Trending prediction markets

prediction_markets_trending
Read-only

Get top trending prediction markets from Polymarket. Returns market questions, current probabilities, volume, liquidity, and outcomes. Filter by category (crypto, politics, sports, tech, culture). Costs $0.005 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (max 25)
sort_byNoSort by: volume or recent_activityvolume
categoryNoFilter: crypto, politics, sports, tech, culture, allall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world profile, and the description adds genuinely new context: the upstream source (Polymarket) and a per-call cost of $0.005 USDC, which materially affects invocation decisions. It omits the definition of "trending" (what time window or ranking basis) and any freshness or rate-limit behavior.

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

Conciseness4/5

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

Three compact sentences with the purpose front-loaded and no filler. The return-fields sentence earns its place given there is no output schema, though the category enumeration is partially duplicated in the schema.

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 zero-required-parameter read tool with no output schema, the description covers purpose, source, return shape, and cost, which is enough to call it correctly. The remaining gap is the undefined notion of "trending" — with several competing prediction-market tools, a time window or ranking basis would sharpen selection.

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 all three parameters (limit, sort_by, category) are already documented, establishing a baseline of 3. The description restates the category values but adds nothing about limit's max of 25 or the default sort by volume, so it does not exceed the schema.

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 and resource ("Get top trending prediction markets from Polymarket") and names the data source, which is more than a restatement of the title. It does not differentiate itself from close siblings such as prediction_market_movers, prediction_market_events, or prediction_market_aggregator, so an agent must infer the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no named alternatives, despite seven related prediction-market siblings in the toolset. The only directional hint is the word "trending" plus the category filter, leaving the choice between this and prediction_market_movers entirely to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources