Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket market

polymarket_market_get
Read-onlyIdempotent

Fetch a Polymarket market's prices, volume, trading rules, and resolution state by market ID, slug, or condition ID to evaluate or monitor a prediction market.

Instructions

Get a Polymarket market's prices, volume, rules and resolution state. Requires marketIdSlugOrConditionId.

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

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.
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.
marketIdSlugOrConditionIdYesRequired. Market id (digits), slug, or condition id (0x and 64 hex digits).

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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the payload facets (prices, volume, rules, resolution state), but says nothing about expensive/open-world behavior, failure modes for an invalid slug, or the conversation_id handshake noted in the schema.

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, front-loaded with the resource and its returned facets. The second sentence largely restates a requirement already enforced by the schema, so it is close to but not entirely free of waste.

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?

No output schema exists, so the description carrying the return facets is valuable, but it omits the required analytics/context parameters and the conversation_id sequencing constraint that shape correct invocation. Adequate for a simple read tool, but not complete.

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 every parameter including the market identifier, locale, and required context/llm_model is already documented. The description only restates that the identifier is required, adding no meaning about accepted formats or id/slug/condition-id distinctions beyond the schema.

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?

Specific verb and resource: "Get a Polymarket market's prices, volume, rules and resolution state" tells an agent exactly what entity and which facets are returned. It does not explicitly differentiate itself from siblings like polymarket_market_stats_get or polymarket_market_resolution_get, which overlap on some of the listed facets.

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?

No when-to-use guidance is given beyond the parameter requirement. An agent gets no signal about when to pick this over polymarket_market_stats_get, polymarket_market_resolution_get, or polymarket_markets_batch_get for the same market.

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