Skip to main content
Glama

Polymarket Resolution Statistics

pm_resolution_stats

Retrieve statistics on Polymarket resolution data including total markets tracked, upcoming resolutions, resolution sources, and last update time.

Instructions

Get statistics about the Polymarket resolution dataset: total markets tracked, upcoming resolutions, resolution sources, and last updated. Free endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for pm_resolution_stats: calls apiGet to /api/v1/pm/resolution/stats, handles errors, and returns JSON-formatted stats data. This is a free endpoint with no input schema.
      async () => {
        const res = await apiGet<PmResolutionStatsResponse>(
          "/api/v1/pm/resolution/stats",
        );
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
          ],
        };
      },
    );
  • PmResolutionStatsResponse interface defining the response shape: dataset, source, update_frequency, and stats (Record<string, unknown>).
    interface PmResolutionStatsResponse {
      dataset: string;
      source: string;
      update_frequency: string;
      stats: Record<string, unknown>;
    }
  • Registration of pm_resolution_stats tool via server.registerTool with title 'Polymarket Resolution Statistics', description explaining it returns dataset statistics (free), and empty inputSchema.
    server.registerTool(
      "pm_resolution_stats",
      {
        title: "Polymarket Resolution Statistics",
        description:
          "Get statistics about the Polymarket resolution dataset: total markets tracked, " +
          "upcoming resolutions, resolution sources, and last updated. Free endpoint.",
        inputSchema: {},
  • src/index.ts:56-56 (registration)
    Top-level registration call: registerPmResolutionTools(server) invoked in the main server setup file.
    registerPmResolutionTools(server);
  • apiGet helper function used by the handler to make HTTP GET requests to the Verilex API.
    export async function apiGet<T = unknown>(
      path: string,
      params?: Record<string, string | number | undefined>,
    ): Promise<ApiResponse<T>> {
      const url = buildUrl(path, params);
    
      const headers: Record<string, string> = {
        Accept: "application/json",
        "User-Agent": "verilex-mcp-server/0.1.0",
      };
    
      // Forward x402 payment token if present in env (for paid endpoints)
      const paymentToken = process.env.VERILEX_PAYMENT_TOKEN;
      if (paymentToken) {
        headers["X-Payment-Token"] = paymentToken;
      }
    
      const res = await fetch(url, { headers });
      const data = (await res.json()) as T;
    
      const stale = res.headers.get("X-Data-Stale");
      const lastUpdated = res.headers.get("X-Data-Last-Updated");
      const ageSeconds = res.headers.get("X-Data-Age-Seconds");
    
      return {
        ok: res.ok,
        status: res.status,
        data,
        stale: stale === "true",
        lastUpdated: lastUpdated ?? undefined,
        ageSeconds: ageSeconds ? Number(ageSeconds) : undefined,
      };
    }
Behavior2/5

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

No annotations are provided, so the description must carry behavioral disclosure. It only mentions 'free endpoint' and 'last updated,' missing details on rate limits, data freshness, or authentication needs. Minimal transparency.

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, no wasted words. The first sentence states the action and content, the second clarifies it is free. Highly efficient.

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?

Given no parameters and no output schema, the description is fairly complete. It covers the main purpose and key data points, though it could mention format or update frequency.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so schema coverage is 100%. The description adds value by listing the specific statistics returned, which goes beyond the schema.

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 provides statistics about the Polymarket resolution dataset, listing specific metrics (total markets tracked, upcoming resolutions, resolution sources, last updated). It distinguishes from siblings like pm_resolution_calendar and pm_stats.

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

Usage Guidelines3/5

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

The description notes it is a free endpoint, implying no cost, but does not specify when to use this tool versus alternatives like pm_resolution_calendar or pm_resolution_lookup. Usage context is implied but not explicit.

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/carrierone/verilexdata-mcp'

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