Skip to main content
Glama
Sign In
mcp-server-polymarket

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search the Polymarket documentation

search_docs
Read-onlyIdempotent

Find Polymarket documentation pages by title and summary to locate relevant guides or API references, then open a chosen result with read_doc.

Instructions

Find pages of the official Polymarket docs (guides and API reference) by title and summary. Read one with read_doc. Cached for a day.

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": {
      "query": "<query>"
    },
    "name": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords to look for, e.g. 'tick size'.
productNoall

Output Schema

NameRequiredDescriptionDefault
resultsYes
total_pagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the bar is lower; the description still adds two traits beyond them: results are matched only on title and summary text (not full body), and responses are 'Cached for a day', which explains potential staleness. It doesn't disclose result ordering or whether matching is fuzzy vs exact, keeping it short of a 5.

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 action and resource, followed by the essential next step and a caching caveat. No filler.

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?

An output schema exists, so return values need no explanation, and the read_doc hand-off completes the workflow. However, for a 3-parameter search tool with 33% schema coverage, the undefined 'product' filter and page-size behavior leave real gaps an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% — only 'query' is described in the schema, while 'limit' and the 'product' enum (all/predictions/perps) have no documentation anywhere. The description uses the phrase 'by title and summary' but explains none of those parameters, so it fails to compensate for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find pages of the official Polymarket docs') and scopes it to guides and API reference, matched 'by title and summary'. The companion sentence 'Read one with read_doc' makes the relationship with the content-fetch sibling explicit, so an agent can separate lookup from retrieval without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context: use this to locate doc pages, then call read_doc to read one — an explicit two-step workflow. It does not say when NOT to use it (e.g. versus the generic 'search' sibling that also exists in the catalog), but within the doc workflow the guidance is unambiguous.

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