Skip to main content
Glama

Smart-money consensus on a market

market_consensus
Read-onlyIdempotent

Smart-money consensus on one Polymarket market versus its current price.

Returns how Smart Money wallets are positioned on one market: how many
hold YES and NO, how much capital each side has invested, the current
market price, and the gap between that positioning and the price.

Two consensus reads are returned side by side and can disagree:
``head_count`` (one Smart Money wallet = one vote; wallets from
OrcaLayer's Smart Money set, so popular markets count thousands) and
``capital_weighted`` (dollars invested per side). In head_count a $5
wallet weighs the same as a $500K one, so it is the weaker of the two
reads; the capital split reflects the money at stake. On cheap longshots
(YES under ~15 cents) head_count leans YES structurally. The divergence
fields measure positioning against the price; they are not evidence that
the price is wrong.

An event slug or event URL (a Polymarket event groups several markets)
returns the event's markets with their ids and Smart Money wallet counts
instead, since the consensus is per market.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market": "<market>"
    },
    "name": "market_consensus"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYesMarket id, Polymarket market or event slug, polymarket.com URL, or 0x condition id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / market / description
      Added value: +"Market id, Polymarket market or event slug, polymarket.com URL, or 0x condition id."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds substantial context beyond them: the two parallel consensus reads, why head_count is the weaker signal, the structural YES bias on sub-15-cent longshots, and an explicit warning that divergence fields are not evidence the price is wrong.

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 core capability is stated in the first sentence, then the return shape, then the interpretive caveats, then the edge case. Every paragraph carries distinct information; there is no restatement of the name, title, or schema fields.

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?

There is no output schema, so the description carries the burden of describing returns and does so concretely (head_count, capital_weighted, price, divergence fields, plus the event-mode variant). For a single-parameter read tool, nothing an agent needs in order to call it or interpret the result is missing.

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

Parameters4/5

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

Schema coverage is 100% and already lists accepted forms (market id, market/event slug, polymarket.com URL, 0x condition id). The description adds meaning the schema does not: that an event slug or event URL changes the result to a list of the event's markets with wallet counts rather than a single consensus.

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 line names a specific verb and resource: smart-money consensus on one Polymarket market versus its current price. It also states what is returned (YES/NO holder counts, capital per side, market price, divergence), which separates it cleanly from siblings like markets, leaderboard, wallet_overview and wallet_positions.

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?

The scope constraint 'on one market' and the fallback behavior for event slugs/URLs give a clear sense of when the tool applies and when its output shape changes. However, no sibling tool is named as an alternative, so the agent must infer that per-wallet detail belongs to wallet_positions rather than being told so.

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.