graph-polymarket-mcp

Overview Schema Source Related Servers Discussions Admin

get_subgraph_schema

Fetch the full GraphQL introspection schema for any Polymarket subgraph (main, activity, orderbook, etc.) to discover available entities and fields for querying prediction market data.

Instructions

Get the full GraphQL schema (introspection) for a Polymarket subgraph

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": {
      "subgraph": "<subgraph>"
    },
    "name": "get_subgraph_schema"
  }
}

Input Schema

Name	Required	Description	Default
`subgraph`	Yes	Subgraph identifier: main, beefy_pnl, slimmed_pnl, activity, or orderbook

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 3, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions 'full schema' indicating a complete introspection response, but does not disclose read-only nature, potential response size, error handling, or any prerequisites. This is minimal for a tool with no annotation support.

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?

The description is a single, concise sentence that front-loads the action and resource with no redundant or filler words. It is appropriately sized for the tool's simplicity.

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?

The tool is simple with one parameter and no output schema. The description adequately states the purpose but lacks details about the response format or how to select a subgraph. Given the minimal complexity, it is sufficient but not comprehensive, leaving some gaps for an agent to fill.

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?

The schema provides an enum for the 'subgraph' parameter with 100% coverage, so the baseline is 3. The tool description adds no additional parameter semantics. However, the schema's description lists only five of the eight enum values, which could be misleading, but that is a schema issue rather than the tool description's responsibility.

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 identifies the action ('get'), the resource ('full GraphQL schema (introspection)'), and the scope ('for a Polymarket subgraph'). It distinguishes this tool from siblings like query_subgraph, which executes queries, and list_subgraphs, which lists available subgraphs.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It only states what it does, leaving the agent to infer usage context.

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