Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket market statistics

polymarket_market_stats_get
Read-onlyIdempotent

Fetch a Polymarket market's open interest and taker volume using its conditionId to assess trading activity and liquidity.

Instructions

Get a Polymarket market's open interest and taker volume. Requires conditionId.

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": {
      "conditionId": "<conditionId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_market_stats_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conditionIdYesRequired. Condition id of the market: 0x followed by 64 hex digits.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the fact that two specific metrics come back, which is useful given there is no output schema, but says nothing about time window, units, or whether volume is cumulative or interval-based.

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?

Two short sentences with the payload statement front-loaded. The second sentence is largely redundant with the schema's required-field list, but nothing is padded or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with full param coverage and annotations carrying the safety profile, this is close to adequate. However, with no output schema the description should say more about what open interest and taker volume represent (window, units) to let an agent interpret results 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% and the conditionId pattern and format are fully documented in the schema. The description only repeats that conditionId is required, adding no meaning beyond the structured field, so the baseline 3 applies.

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 a Polymarket market's) plus the two metrics returned (open interest and taker volume). This distinguishes it from polymarket_market_get and polymarket_user_stats_get by name of metric, though it never explicitly contrasts with those siblings.

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?

"Requires `conditionId`" is a prerequisite restatement, not usage guidance. The description offers no when-to-use context, no exclusion, and no pointer to alternatives such as polymarket_market_price_history_list or polymarket_market_get for other market data.

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

Deploy Server

Other Tools