Skip to main content
Glama

search_us_npi_providers

Search U.S. physicians, dentists, clinics, hospitals, and pharmacies through the CMS NPPES NPI Registry by NPI, specialty, city, state, or organization; returns specialty and contact details.

Instructions

Search 8,000,000+ U.S. physicians, dentists, clinics, hospitals & pharmacies via official U.S. CMS NPPES NPI Registry API v2.1 (returns NPI, specialty, practice phone/fax, address & authorized official).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_us_npi_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional U.S. city name (e.g. 'Los Angeles', 'Austin').
limitNoMax providers (1 to 25, default 5).
stateNo2-letter U.S. state code (e.g. 'CA', 'NY', 'TX').
specialtyNoMedical specialty / taxonomy (e.g. 'Cardiology', 'Dentist', 'Dermatology').
npi_numberNoOptional exact 10-digit NPI lookup.
organization_nameNoOptional clinic/hospital organization name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the authoritative data source ('official U.S. CMS NPPES NPI Registry API v2.1') and the returned fields (NPI, specialty, phone/fax, address, authorized official), which is genuinely useful. It omits whether authentication/API keys are needed, rate limits, pagination behavior, and what happens on no-match.

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?

A single front-loaded sentence with zero filler; the scale, source, and return contents are all packed efficiently, and the parenthetical keeps return-value detail out of the way of the core purpose.

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?

There is no output schema, and the description partially compensates by naming the returned fields. However, for a six-parameter search with no annotations it leaves gaps: no auth requirement, no pagination or result-count behavior, and no statement on how multiple filters combine.

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 description coverage is 100% and each of the six optional parameters is documented in the schema with format examples, so the baseline of 3 applies. The description adds no parameter-level meaning beyond that, such as whether filters are AND-combined or how NPI lookup interacts with the other filters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs the specific verb 'Search' with a concrete resource and scope: '8,000,000+ U.S. physicians, dentists, clinics, hospitals & pharmacies' from the CMS NPPES NPI Registry v2.1. The healthcare-provider domain inherently separates it from the sibling tools (clinical trials, EU tenders, French companies), though no sibling is named explicitly.

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?

Usage is only implied: the parameter list suggests looking up providers by city/state/specialty/NPI, but the description never states when to use this versus another tool, nor any exclusions or prerequisites. With siblings in unrelated domains this is low-risk, but the guidance itself is absent.

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