Skip to main content
Glama

NPI Dataset Statistics

npi_stats

Retrieve statistics for the NPI dataset: total record count, states covered, last update timestamp, and data source. Free endpoint, no payment needed.

Instructions

Get statistics about the NPI dataset: total record count, number of states, last updated timestamp, and data source information. Free endpoint, no payment required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function for the npi_stats tool. Calls the API endpoint /api/v1/npi/stats and returns the JSON response containing dataset statistics (record count, last updated, etc.).
      async () => {
        const res = await apiGet<NpiStatsResponse>("/api/v1/npi/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) },
          ],
        };
      },
    );
  • The NpiStatsResponse interface defines the shape of the API response: dataset, source, update_frequency, and a stats object.
    interface NpiStatsResponse {
      dataset: string;
      source: string;
      update_frequency: string;
      stats: Record<string, unknown>;
    }
  • Registration of the npi_stats tool on the MCP server via server.registerTool(), with the name 'npi_stats', a title, description, and an empty input schema.
    server.registerTool(
      "npi_stats",
      {
        title: "NPI Dataset Statistics",
        description:
          "Get statistics about the NPI dataset: total record count, number of states, " +
          "last updated timestamp, and data source information. Free endpoint, no payment required.",
        inputSchema: {},
      },
  • src/index.ts:39-39 (registration)
    Call to registerNpiTools(server) in the main entry point, which wires up the npi_stats tool (along with query_npi_providers and lookup_npi) into the MCP server.
    registerNpiTools(server);
  • The apiGet helper function used by the npi_stats handler to make the HTTP GET request 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,
      };
    }
Behavior3/5

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

No annotations provided, so description carries the burden. It discloses it's free and what data it returns, but does not mention any behavioral traits like read-only, rate limits, or auth requirements. Adequate for a simple stats retrieval but not comprehensive.

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 with no wasted words. Front-loaded with core purpose, then adds the free usage note. Efficiently conveys all necessary information.

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?

No output schema, but description lists the returned fields (record count, number of states, last updated, data source). For a simple stats endpoint, this is sufficient context. Could mention format or pagination but not required.

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?

Input schema has zero parameters with 100% coverage. According to rules, 0 params baseline is 4. The description correctly implies no inputs needed.

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?

States it gets statistics about the NPI dataset with specific items: total record count, number of states, last updated timestamp, data source info. Clearly distinguishes from sibling stats tools like contract_stats or crypto_stats.

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?

Explicitly notes it's a free endpoint with no payment required, which is a usage guideline. However, it does not explicitly state when to use this tool versus alternatives like lookup_npi for individual provider details.

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