Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket US market

polymarket_us_market_get
Read-onlyIdempotent

Retrieve one Polymarket US market by ID or slug, with optional order-book data for pricing and liquidity checks.

Instructions

Get one market on the Polymarket US exchange, with its order book on request. Requires idOrSlug.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNo`book` adds the order book (one more lookup).
idOrSlugYesRequired. US exchange market id (digits) or slug.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds only the fact that order-book retrieval is optional and that it costs "one more lookup" context, which is thin but consistent. No contradiction with annotations.

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 core action and venue scope front-loaded and no filler. The trailing "Requires `idOrSlug`" duplicates the schema's required list, which is a minor redundancy but arguably useful as a call-time reminder.

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 simple single-entity read with a 100%-covered schema and rich annotations, the description supplies enough to call correctly. No output schema exists, but the description indicates what is returned (a market, optionally its order book), so nothing essential is missing.

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 schema already documents idOrSlug, include, context, llm_model, and conversation_id in detail. The description restates that idOrSlug is required and that the book is optional, adding no format, slug-vs-id, or lookup-cost detail beyond what the schema provides. 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?

The description gives a specific verb and resource ("Get one market") and qualifies the venue as "the Polymarket US exchange," which lets an agent distinguish it from the global-exchange sibling polymarket_market_get without opening either schema. It does not name that sibling explicitly, so it stops short of a 5.

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?

The US-exchange qualifier implies the context in which this tool applies, and "with its order book on request" hints at the include option. However, there is no explicit statement of when to prefer this over polymarket_market_get, polymarket_us_event_get, or the batch getter, and no exclusions or prerequisites beyond the required idOrSlug.

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