Fetch Polymarket market data, including outcomes and volumes, from the Main subgraph. Use parameters to limit the number of results and customize ordering.
Get Polymarket market/condition data including outcomes and volumes from the Main subgraph
| Name | Required | Description | Default |
|---|---|---|---|
| first | No | Number of markets to return (1-100) | |
| orderBy | No | Field to order by | id |
| orderDirection | No | Sort direction | desc |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose any behavioral traits like permissions, rate limits, or data scope beyond the minimal 'outcomes and volumes'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence efficiently conveys the tool's purpose with no unnecessary words, well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Description is adequate but does not elaborate on how this tool differs from the many sibling get_* tools; lacks completeness in guiding selection choice.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers all parameters with descriptions, so the description adds no extra meaning beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool gets market/condition data including outcomes and volumes, specifying the source subgraph, which distinguishes it from siblings like get_market_info.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives such as get_market_info or search_markets; the description lacks any contextual usage advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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