Skip to main content
Glama
PaulieB14

graph-polymarket-mcp

by PaulieB14

search_markets_enriched

Search Polymarket markets and enrich each result with live prices and resolution status in one call.

Instructions

Power tool: search Polymarket markets then auto-enrich each result with live CLOB prices and on-chain resolution status. Combines Gamma API + CLOB API + The Graph in one call — no need to chain tools manually.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results (1-20, kept small for enrichment speed)
queryYesSearch text (e.g. 'Trump', 'Bitcoin', 'World Cup')
activeNoFilter: only active markets
closedNoFilter: only closed/resolved markets
Behavior3/5

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

With no annotations, the description carries full burden. It discloses combining three APIs but does not mention failure modes, rate limits, or partial failures during enrichment.

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, front-loaded with purpose, no wasted words.

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?

Given complexity of multi-API enrichment and no output schema, the description explains what enrichment includes but lacks details on output structure or potential errors.

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 coverage is 100%, and schema descriptions are adequate. The description adds minimal extra meaning beyond what schema provides.

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?

The description clearly states the tool searches Polymarket markets and enriches them with CLOB prices and resolution status. It explicitly distinguishes from manual chaining and sibling tools like search_markets (basic).

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?

The description says 'no need to chain tools manually,' implying use when enrichment is needed. However, it does not provide explicit when-not-to-use guidance or alternative tools for simpler cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaulieB14/graph-polymarket-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server