Skip to main content
Glama

Get Polymarket High-Volume Prediction Markets & Arbitrage Spreads

get_polymarket_alpha
Read-onlyIdempotent

Fetch high-volume active Polymarket prediction markets with outcome probabilities, USD liquidity depth, and binary arbitrage spreads to identify trading opportunities.

Instructions

Retrieves the highest-volume active prediction markets on Polymarket along with outcome probabilities, liquidity depth in USD, and binary arbitrage spreads. Free to start with zero wallet or setup required (3 free queries/day); unlimited calls supported via optional Base prepaid session.

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

Input Schema

NameRequiredDescriptionDefault
paymentProofNoOptional Base USDC transaction hash ("0x...") for high-frequency trading bots needing unlimited calls. Leave empty for automatic free daily queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.1
    • changedInput schema / properties / paymentProof / description
      Previous value: -"Optional Base USDC transaction hash (\"0x...\") or HTTP 402 payment proof for unlimited calls after your 3 free daily queries."New value: +"Optional Base USDC transaction hash (\"0x...\") for high-frequency trading bots needing unlimited calls. Leave empty for automatic free daily queries."
  2. Changed2 schema fields changedv1.6.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / paymentProof
      Added value: +{
      +  "description": "Optional Base USDC transaction hash (\"0x...\") or HTTP 402 payment proof for unlimited calls after your 3 free daily queries.",
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond annotations: a 3-free-queries-per-day limit, zero wallet/setup for free use, and an optional Base prepaid session for unlimited calls. It does not cover data freshness or result-size limits, but the added rate-limit and payment details are valuable.

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 two tight sentences: the first front-loads the core purpose and returned data, and the second adds essential access/payment context. Every sentence earns its place with no wasted wording.

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 no output schema, the description does a good job naming the key return fields (outcome probabilities, liquidity depth, arbitrage spreads) and explaining access constraints. It could be slightly more complete by specifying how many markets are returned or the ordering, but it is sufficient for an agent to call the tool correctly.

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 the single optional paymentProof parameter is already fully documented in the schema. The description reinforces the free-vs-prepaid distinction but adds no new syntax or format details beyond what the schema provides, making the baseline 3 appropriate.

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 uses a specific verb ('Retrieves') and clearly names the resource ('highest-volume active prediction markets on Polymarket') plus the key data returned (outcome probabilities, liquidity depth, arbitrage spreads). This is easily distinguishable from the sibling tools, which cover token security, token alpha, new pairs, and payment info.

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 when to use it by stating it retrieves Polymarket prediction market alpha, and it explains the free/prepaid access model. However, it does not explicitly compare this tool to alternatives or state when not to use it, leaving usage guidance at an implied level.

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