Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket market resolution

polymarket_market_resolution_get
Read-onlyIdempotent

Retrieve how a Polymarket market resolved or is resolving, including the oracle’s record, by supplying its condition ID.

Instructions

Get how a Polymarket market resolved or is resolving, with the oracle's record. 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_resolution_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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value by noting it returns the oracle's record and works for both already-resolved and still-resolving markets, but it says nothing about the shape of that record or how unresolved markets are represented.

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 capability and followed by the hard requirement; no filler. The 'Requires conditionId' clause is slightly redundant with the schema's required list, costing a point.

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

Completeness4/5

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

For a single-resource read tool with full annotation coverage and a fully documented schema, the description covers purpose and the key returned artifact (the oracle record). With no output schema, a brief note on what the resolution record contains or how pending markets appear would close the remaining gap.

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 every parameter (including conditionId, context, llm_model and conversation_id) is documented in the schema itself. The description only restates that conditionId is required, adding no format or usage detail beyond the schema's regex note.

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 states a specific verb and resource: get how a market 'resolved or is resolving' along with 'the oracle's record'. That distinguishes it from the metadata-oriented sibling polymarket_market_get, though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance, and the closest overlapping sibling (polymarket_market_get) is not addressed. The only implicit signal is that the tool concerns resolution state, so an agent must infer that it should be called instead of the general market lookup for settlement questions.

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