Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket prices

polymarket_prices_get
Read-onlyIdempotent

Retrieve Polymarket prices for up to 150 outcome token IDs in one request to compare market outcomes and reduce API calls.

Instructions

Get Polymarket prices for up to 150 outcome tokens in one request. Requires tokenIds.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
tokenIdsYesRequired. Outcome token ids, 1–150. Repeat the parameter or separate ids with commas. Token ids are the `tokenId` of a market outcome.
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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds only that batching up to 150 tokens in one request is possible, without noting rate limits, whether prices are last-trade vs mid, or staleness. Modest value beyond structured fields.

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?

Two short sentences, front-loaded with the capability and the batching limit, with zero redundant wording. Nothing could be removed without losing information.

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 schema coverage and rich annotations, the essentials for calling are present. However, with no output schema, the description gives no hint of what a price result contains (price field, side, timestamp), leaving the agent to discover the response shape empirically.

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: the schema already explains tokenIds format, the 1–150 range, and the context/llm_model/conversation_id conventions. The description merely echoes the tokenIds requirement and the 150 cap, adding no new meaning.

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 Polymarket prices for outcome tokens) plus a meaningful scope detail (up to 150 tokens in one request). It does not distinguish itself from siblings like polymarket_books_get or polymarket_market_price_history_list, so an agent must infer when a batch snapshot beats a book or history call.

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?

The only usage signal is 'Requires tokenIds', which restates the schema. There is no statement of when to use this batched price lookup versus polymarket_books_get, polymarket_market_get, or polymarket_market_price_history_list, and no exclusions or prerequisites about token id provenance beyond the schema note.

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