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

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get quotes

get_quotes
Read-onlyIdempotent

Retrieve best bid/ask, midpoint, spread, top sizes, and last trade for up to 50 tokens in one call to assess current market quotes; use order-book tools for depth.

Instructions

Best bid and ask, midpoint, spread, top sizes and last trade for each token, in one call. Use get_order_books for depth.

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": {
      "token_ids": "<token_ids>"
    },
    "name": "get_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_idsYesToken ids.

Output Schema

NameRequiredDescriptionDefault
quotesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the behavioral point that the data is consolidated into a single call per token set, but it does not mention rate limits, the 50-token cap, partial/missing quote behavior, or staleness/latency — the traits that actually matter for a market-data read.

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 sentences, zero filler, with the payload contents front-loaded and the routing hint last. Every clause earns its place.

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?

With an output schema present, the description needn't document return structure, and the annotations cover safety, so the essentials are there for a one-parameter read. Minor gaps: no mention of batching limits or how missing/illiquid tokens appear in the response, which matters for a 50-id batch call.

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 the only parameter is a token id array, so the schema carries the burden (including minItems/maxItems bounds). The phrase 'for each token' adds the useful batch semantic that results are keyed per requested id, but nothing else beyond the schema. Baseline 3 applies.

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?

Names the exact fields returned (best bid/ask, midpoint, spread, top sizes, last trade) scoped 'for each token, in one call', which pins down a batched top-of-book snapshot rather than an order book or trade history. It explicitly distinguishes itself from get_order_books, so an agent can separate the two 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?

Provides a clear selection rule: use this for best-price summary, use get_order_books when depth is needed. That is an explicit alternative with a condition. It stops short of stating exclusions or edge cases (e.g. what to do when tokens have no quote), so not a full 5.

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