Skip to main content
Glama

Verify NPI numbers

verify_npi_numbers
Read-onlyIdempotent

Use this when the user wants an npi lookup, verify npi number, bulk npi lookup or npi taxonomy code lookup for credentialing. Reads live public registry records, checks optional expected names, states and taxonomies, and returns Excel and CSV downloads. Up to 40 NPIs per call; check digits cannot prove issuance. Do not use for patient records or proof of licensure.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "providers": "<providers>"
    },
    "name": "verify_npi_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
providersYesRoster of 1 to 40 providers, e.g. [{"npi":"1245319599","expected_state":"VA"}].

Output Schema

NameRequiredDescriptionDefault
sourceYes
summaryYes
searchesYes
downloadsYes
providersYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/idempotent/destructive, and the description still adds real context: live public registry reads, batch limit of 40 per call, Excel and CSV downloads, and the caveat that check digits cannot prove issuance. It does not mention error/partial-failure behavior for mixed rosters.

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 use case and search-keyword variants, then constraints and exclusions. Dense but every clause carries information; the keyword list is slightly stuffed but serves retrieval.

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?

Output schema exists so return values needn't be explained, and annotations cover the safety profile; the description still covers the batch cap and the important caveat about check digits. The only gap is not distinguishing itself from search_npi_providers for single-provider lookups.

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% and the nested provider fields (npi, expected_name, expected_state, expected_taxonomy) are already documented, so the description only loosely restates them. Baseline 3 is appropriate; it adds no format or matching-behavior detail beyond the schema.

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?

Specific verb+resource ('npi lookup / verify npi number / bulk npi lookup / npi taxonomy code lookup') with scope stated. It does not explicitly contrast with the sibling search_npi_providers, so the verify-vs-search distinction is left implicit.

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?

Gives clear trigger phrasing (credentialing lookup) and explicit exclusions ('Do not use for patient records or proof of licensure'). It stops short of naming search_npi_providers as the alternative when the user merely wants to find providers, so the sibling routing is missing.

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