Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket biggest movers

polymarket_movers_list
Read-onlyIdempotent

Identify Polymarket markets with significant price movement and retrieve short price histories, with optional category filters and locale translations.

Instructions

List the Polymarket markets whose price moved most, with short price histories. Optional inputs: category and locale. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
localeNoTranslate titles and market questions into this language. Descriptions stay in English.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
categoryNoOnly markets in this category: `politics`, `sports`, `crypto`, `finance`, `tech`, `culture` or `world`. Any other value is rejected. Default: all.
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.
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.4/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 fully covered. The description adds one useful behavioral fact beyond that — results include short price histories — but says nothing about ranking metric, ordering, result limits, or pagination, which are the questions an agent actually has for a "movers" tool.

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?

Three short sentences, front-loaded with the core purpose, with no rambling. "Returns a list" is near-filler and there is no output schema, so that sentence is a missed opportunity rather than waste, but the text is otherwise tight.

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?

The tool is simple and the schema is fully annotated, so the description is nearly sufficient. However, it labels only category and locale as inputs while omitting the required context and llm_model meta-parameters and the conversation_id sequencing rule, which are the most error-prone parts of calling this tool.

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 schema documents category (with its full enum and rejection rule), locale (translation scope), and the meta-parameters in more detail than the description. The description only echoes that category and locale exist and are optional, adding no semantic value; baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb and resource ("List the Polymarket markets whose price moved most") plus the distinctive qualifier "with short price histories," which separates it from polymarket_markets_list and polymarket_market_price_history_list. It stops short of naming any sibling explicitly, so it is clear but not maximally differentiated.

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?

Usage is only implied: an agent can infer this is for discovering top price gainers/losers in a window, but there is no statement of when to prefer it over polymarket_markets_list or polymarket_market_price_history_list, and no exclusions or prerequisites. No mention of ranking direction, time window, or result count.

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