Skip to main content
Glama

Find a US healthcare provider by NPI or name

npi
Read-only

US healthcare providers from the NPPES NPI Registry: look up one by its 10-digit NPI (check digit verified) or search by name with an optional state. Each provider gives type, name, credential, status, primary taxonomy and practice address. Information only, not medical advice. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "npi"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFirst and last name, or last name
stateNoTwo-letter US state, e.g. CA
numberNo10-digit NPI

Output Schema

NameRequiredDescriptionDefault
queryNo
sourceNo
checkedAtNo
providersNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the monetization model ($0.002 per successful call via x402 in USDC across Base, Solana and 10 more networks) and that failed calls are not charged — critical for an agent deciding to invoke. It also adds check-digit verification on NPI input, the fields returned per provider, and an informational-only disclaimer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the capability and mode selection, then the return fields, then pricing. Every sentence carries information, though the pricing/disclaimer tail makes it a long single paragraph where a short break would aid scanning.

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 three-optional-parameter lookup with an output schema present, the definition covers source, modes, returned fields, validation behavior, and cost model. Nothing an agent needs to call it correctly or predict the charge is missing.

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?

Schema coverage is already 100%, so the baseline is 3; the description adds real meaning on top by noting the NPI must be 10 digits and is check-digit verified, and by framing state as optional in search mode. It does not clarify name-match semantics (partial vs. exact, ordering) beyond what the schema says.

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+resource: US healthcare providers from the NPPES NPI Registry, with two explicit access modes (exact 10-digit NPI lookup vs. name search). The title and first sentence together make the domain, data source, and supported operations unmistakable.

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?

It clearly explains how to choose between the two modes: supply the 10-digit NPI for a single lookup, or use name with an optional state for a search. It does not name sibling tools or state when this tool is the wrong choice, so it stops short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources