Skip to main content
Glama

Market search

markets
Read-onlyIdempotent

Search Polymarket markets, optionally where Smart Money wallets cluster.

Finds markets by topic, slug or URL and shows how many wallets from
OrcaLayer's Smart Money set hold each side right now. Returns each
market's id, question, YES price, smart_wallets_yes / smart_wallets_no,
volume, end date and days left. The counts are wallets, whatever their
position size; popular markets have thousands. The dollar split on one
market is in the market_consensus tool.

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

Input Schema

NameRequiredDescriptionDefault
qNoFree-text query; also accepts a Polymarket URL or slug. "" browses. Open markets only.
limitNoHow many markets to return, 1 to 50 (larger values return 50).
categoryNoRestrict to one market category: "Crypto", "Politics", "Sports", "Esports", "Geopolitics", "Economics", "Tech/AI", "Culture" or "Weather" (case-insensitive; "tech" and "ai" also work). Omit for all categories.
min_volumeNoMinimum market volume in USD. Omit for no minimum.
min_whalesNoMinimum number of Smart Money wallets holding a position in the market (either side). Omit for no minimum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Restrict to one market category: \"Crypto\", \"Politics\", \"Sports\", \"Geopolitics\", \"Economics\" or \"Tech/AI\" (case-insensitive; \"tech\" and \"ai\" also work). Omit for all categories."New value: +"Restrict to one market category: \"Crypto\", \"Politics\", \"Sports\", \"Esports\", \"Geopolitics\", \"Economics\", \"Tech/AI\", \"Culture\" or \"Weather\" (case-insensitive; \"tech\" and \"ai\" also work). Omit for all categories."
  2. Changed5 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Restrict to one market category: \"Crypto\", \"Politics\", \"Sports\", \"Geopolitics\", \"Economics\" or \"Tech/AI\" (case-insensitive; \"tech\" and \"ai\" also work). Omit for all categories."
    • addedInput schema / properties / limit / description
      Added value: +"How many markets to return, 1 to 50 (larger values return 50)."
    • addedInput schema / properties / min_volume / description
      Added value: +"Minimum market volume in USD. Omit for no minimum."
    • addedInput schema / properties / min_whales / description
      Added value: +"Minimum number of Smart Money wallets holding a position in the market (either side). Omit for no minimum."
    • addedInput schema / properties / q / description
      Added value: +"Free-text query; also accepts a Polymarket URL or slug. \"\" browses. Open markets only."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, so the bar is lower, yet the description adds real guidance: counts are wallets irrespective of position size, and popular markets run into the thousands, which calibrates expectations for the returned numbers. It also discloses the return field set, though nothing about pagination or ordering.

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?

It is front-loaded with the core action and then the payload contents, with no filler sentences. The trailing line break and the slightly fragmentary enumeration of returned fields cost it a point but nothing is wasted.

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?

With no output schema, the description carries the burden of describing returns, and it does so by enumerating id, question, YES price, wallet counts, volume, end date and days left. Combined with full schema coverage on all five optional parameters, an agent has enough to call it 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 coverage is 100%, so the schema already documents q, limit, category, min_volume and min_whales fully, including that q accepts a URL or slug and that empty string browses. The description restates the topic/slug/URL capability but adds no semantics beyond it, so the baseline of 3 applies.

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 opening sentence gives a specific verb and resource ("Search Polymarket markets") plus a scope qualifier (Smart Money clustering), and it explicitly separates itself from the sibling market_consensus. An agent can distinguish it from leaderboard/wallet_positions by the fact it returns market rows rather than wallet or position data.

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?

It names the alternative explicitly and the condition that selects it: the dollar split on one market belongs to market_consensus. It also clarifies that results are limited to open markets. There is no explicit statement of when not to use it (e.g. versus wallet_positions) but the guidance given is concrete.

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.