Skip to main content
Glama

Polymarket scanner

polymarket_scanner
Read-onlyIdempotent

Live Polymarket Gamma scanner: filter active prediction markets by keyword/minVolume/sort for YES/NO implied probabilities, 24h volume, liquidity, 1d/1w moves, spread bps, and CLOB token IDs. $0.002 per call over x402 or X-API-Key. Not advice.

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

Input Schema

NameRequiredDescriptionDefault
qNoOptional keyword filter (e.g. fed, bitcoin, election).
sortNoSort order (default volume24hr).
limitNoMax markets (default 15, max 40).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
minVolumeNoMinimum 24h USD volume (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely non-structured context: the cost model ($0.002 per call), the two auth paths (x402 payment payload or X-API-Key), and a 'Not advice' disclaimer. What it omits is failure behavior when payment is missing or the limit cap is hit.

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?

A single dense sentence with the capability front-loaded, followed by cost/auth and a short disclaimer — every clause carries information. The return-field list is long but earns its place since there is no output 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?

With no output schema, the description usefully enumerates return fields, and it discloses the payment/auth prerequisite that an agent must satisfy before calling. Remaining gaps are minor: no note on what happens without payment, no pagination/limit-cap behavior, and no guidance on choosing between this and the orderbook sibling.

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 baseline is 3 and the schema already documents q, sort, limit, minVolume, and the payment payload. The description restates keyword/minVolume/sort and gestures at the payment mechanism but adds no format or interaction detail beyond 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?

The description leads with a specific verb+resource ('Live Polymarket Gamma scanner: filter active prediction markets') and enumerates the returned signals (implied probabilities, volume, liquidity, moves, spread bps, CLOB token IDs), so an agent knows exactly what the tool produces. It implicitly separates itself from kalshi_scanner by scoping to Polymarket, but never explicitly routes against polymarket_orderbook or kalshi_scanner.

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?

Use context is implied by 'filter active prediction markets by keyword/minVolume/sort' and by the paid-per-call framing, but there is no explicit when-to-use/when-not or pointer to a sibling such as polymarket_orderbook for depth data. The agent must infer the boundary itself.

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