Skip to main content
Glama
PaulieB14

graph-polymarket-mcp

get_subgraph_schema

Retrieve the complete GraphQL schema for any Polymarket subgraph to understand available queries and data structures.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subgraphYesSubgraph identifier: main, beefy_pnl, slimmed_pnl, activity, or orderbook

Implementation Reference

  • src/index.ts:69-100 (registration)
    Registration of the 'get_subgraph_schema' tool with its input schema and handler
    server.registerTool(
      "get_subgraph_schema",
      {
        description: "Get the full GraphQL schema (introspection) for a Polymarket subgraph",
        inputSchema: {
          subgraph: z
            .enum(SUBGRAPH_NAMES)
            .describe("Subgraph identifier: main, beefy_pnl, slimmed_pnl, activity, or orderbook"),
        },
      },
      async ({ subgraph }) => {
        try {
          const cfg = SUBGRAPHS[subgraph];
          const introspectionQuery = `{
            __schema {
              types {
                name
                kind
                fields {
                  name
                  type { name kind ofType { name kind } }
                }
              }
            }
          }`;
          const data = await querySubgraph(cfg.ipfsHash, introspectionQuery);
          return textResult(data);
        } catch (error) {
          return errorResult(error);
        }
      }
    );
Behavior3/5

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

The description implies a read-only operation without stating it explicitly. Since there are no annotations, the description could improve by confirming no side effects or data modifications.

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 single sentence is concise and front-loaded with the core action and resource. No unnecessary words are present.

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 description omits details about the return format (e.g., JSON introspection result). Given the absence of an output schema, users might benefit from knowing what to expect.

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 parameter 'subgraph' is already thoroughly described in the input schema (enum values listed). The tool description adds no further semantic value beyond the schema's own description.

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 action ('Get') and the resource ('full GraphQL schema (introspection) for a Polymarket subgraph'). It uniquely identifies the tool's purpose and implicitly distinguishes it from siblings like 'query_subgraph'.

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?

No guidance is provided on when to use this tool versus alternatives such as 'query_subgraph' or 'list_subgraphs'. There is no mention of prerequisites, context, or exclusions.

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