Skip to main content
Glama

NPPES NPI Registry MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Search the NPI registry (all criteria)

nppes_search
Read-only

Full-power search of the NPPES NPI Registry across ANY combination of criteria — individual name, organization name, NPI number, taxonomy/specialty, and location. Use nppes_search_individuals / nppes_search_organizations for the common cases; use this when you need mixed or advanced criteria. The API requires at least one meaningful search parameter. NPPES Read API v2.1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity of the provider's address.
skipNoNumber of records to skip, for pagination (0–1000; combined with limit, up to 1200 records reachable).
limitNoMax number of records to return (1–200, default 10).
stateNoTwo-letter U.S. state/territory abbreviation, e.g. 'CA', 'NY', 'PR'.
numberNoExact 10-digit NPI number.
last_nameNoIndividual provider last name (trailing '*' wildcard allowed).
first_nameNoIndividual provider first name (trailing '*' wildcard allowed).
postal_codeNoPostal (ZIP) code; a trailing '*' wildcard is allowed for prefix search, e.g. '941*'.
country_codeNoTwo-letter country code (default 'US'). Use 'US' for domestic addresses.
name_purposeNoFor name matching: 'PROVIDER' (default) or 'AO' (authorized official).
address_purposeNoWhich address the city/state/postal_code filters apply to (LOCATION = practice address).
enumeration_typeNoRestrict to 'NPI-1' (individuals) or 'NPI-2' (organizations). Omit to search both.
organization_nameNoOrganization name (trailing '*' wildcard allowed).
taxonomy_descriptionNoProvider taxonomy / specialty text, e.g. 'cardiology', 'Pediatrics', 'Social Worker'. Partial matches supported; a trailing '*' wildcard is allowed (min 2 chars before it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description usefully adds the invocation constraint that at least one meaningful parameter is required and pins the backing API version (NPPES Read API v2.1). It does not discuss rate limits, result caps, or pagination behavior, but skip/limit semantics are already covered in the schema.

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?

Three sentences, each earning its place: capability, routing decision, and precondition, in that order. No filler and the most decision-relevant content leads.

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?

For a read-only search with a fully documented 14-parameter schema and no output schema, the description covers capability, routing, and the one hard API constraint. It stops short of describing result shape or ordering, which is a minor gap against the tool's breadth.

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?

Schema coverage is 100% across all 14 parameters, with enums and wildcard/pagination rules documented in-schema, so the baseline is 3. The description only categorizes the criteria axes and adds no syntax, format, or interaction detail beyond what the schema already provides.

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 a specific verb and resource ('Full-power search of the NPPES NPI Registry') and enumerates the criteria axes it spans (name, organization, NPI, taxonomy, location). It explicitly names the two sibling tools it is not, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Names the alternatives ('nppes_search_individuals / nppes_search_organizations for the common cases') and the exact condition that selects this one ('when you need mixed or advanced criteria'). It also states a hard precondition: the API requires at least one meaningful search parameter.

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

All NPPES NPI Registry MCP by usefulapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources