Skip to main content
Glama

PACER Dataset Statistics

pacer_stats

Get PACER court records statistics: total cases, courts covered, date range, and last updated timestamp.

Instructions

Get statistics about the PACER court records dataset: total cases indexed, courts covered, date range, and last updated timestamp. Free endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the pacer_stats tool. Calls the API endpoint /api/v1/pacer/stats, handles 404 (dataset not available) and other errors, and returns the stats JSON on success.
      async () => {
        const res = await apiGet<PacerStatsResponse>("/api/v1/pacer/stats");
    
        if (!res.ok) {
          if (res.status === 404) {
            return {
              content: [
                {
                  type: "text" as const,
                  text: "PACER dataset is not yet available. This data source is coming soon.",
                },
              ],
            };
          }
          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) },
          ],
        };
      },
    );
  • The PacerStatsResponse interface defining the shape of the API response (dataset, source, update_frequency, stats).
    interface PacerStatsResponse {
      dataset: string;
      source: string;
      update_frequency: string;
      stats: Record<string, unknown>;
    }
  • The input schema for pacer_stats — an empty object (no parameters required). Also includes title and description metadata.
    {
      title: "PACER Dataset Statistics",
      description:
        "Get statistics about the PACER court records dataset: total cases indexed, " +
        "courts covered, date range, and last updated timestamp. Free endpoint.",
      inputSchema: {},
    },
  • The server.registerTool('pacer_stats', ...) call that registers the tool with the MCP server, binding the schema and handler.
    server.registerTool(
      "pacer_stats",
      {
        title: "PACER Dataset Statistics",
        description:
          "Get statistics about the PACER court records dataset: total cases indexed, " +
          "courts covered, date range, and last updated timestamp. Free endpoint.",
        inputSchema: {},
      },
      async () => {
        const res = await apiGet<PacerStatsResponse>("/api/v1/pacer/stats");
    
        if (!res.ok) {
          if (res.status === 404) {
            return {
              content: [
                {
                  type: "text" as const,
                  text: "PACER dataset is not yet available. This data source is coming soon.",
                },
              ],
            };
          }
          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) },
          ],
        };
      },
    );
  • src/index.ts:14-58 (registration)
    Import of registerPacerTools and its invocation (line 41) in the main server setup, which registers all PACER tools including pacer_stats.
    import { registerPacerTools } from "./tools/pacer.js";
    import { registerWeatherTools } from "./tools/weather.js";
    import { registerOtcTools } from "./tools/otc.js";
    import { registerTrademarkTools } from "./tools/trademarks.js";
    import { registerPatentTools } from "./tools/patents.js";
    import { registerCompanyTools } from "./tools/company.js";
    import { registerCryptoTools } from "./tools/crypto.js";
    import { registerSanctionsTools } from "./tools/sanctions.js";
    import { registerWhaleTools } from "./tools/whales.js";
    import { registerLabelTools } from "./tools/labels.js";
    import { registerHolderTools } from "./tools/holders.js";
    import { registerDexTools } from "./tools/dex.js";
    import { registerContractTools } from "./tools/contracts.js";
    import { registerPmTools } from "./tools/pm.js";
    import { registerPmArbTools } from "./tools/pm_arb.js";
    import { registerPmResolutionTools } from "./tools/pm_resolution.js";
    import { registerEconTools } from "./tools/econ.js";
    import { registerPmMicroTools } from "./tools/pm_micro.js";
    
    function createMcpServer() {
      const server = new McpServer({
        name: "verilex-data",
        version: "0.3.3",
      });
    
      registerNpiTools(server);
      registerSecTools(server);
      registerPacerTools(server);
      registerWeatherTools(server);
      registerOtcTools(server);
      registerTrademarkTools(server);
      registerPatentTools(server);
      registerCompanyTools(server);
      registerCryptoTools(server);
      registerSanctionsTools(server);
      registerWhaleTools(server);
      registerLabelTools(server);
      registerHolderTools(server);
      registerDexTools(server);
      registerContractTools(server);
      registerPmTools(server);
      registerPmArbTools(server);
      registerPmResolutionTools(server);
      registerEconTools(server);
      registerPmMicroTools(server);
Behavior4/5

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

No annotations provided, but the description explicitly states 'Free endpoint', indicating no cost. Since the tool has no parameters and is read-only, no additional behavioral disclosure is needed beyond what's described.

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 two sentences, front-loading the key information about what stats are returned, then adding a note about being free. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple stateless tool with no parameters and no output schema, the description fully covers what the tool does and what it returns. No gaps remain.

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 the description does not need to add parameter meaning. The schema covers 100% of parameters (none), and a baseline of 4 is appropriate for no parameters.

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 returns statistics about the PACER dataset, listing specific fields (total cases, courts, date range, last updated). It uniquely identifies its target dataset, distinguishing it from sibling stats tools for other datasets.

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 implies usage context (getting dataset-level stats) but does not explicitly exclude alternatives or state when not to use. However, given the tool's simplicity and zero parameters, the guidance is adequate.

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