Skip to main content
Glama

SolvingHealth federal health data

find_providers

Search the CMS NPPES NPI registry for clinicians or organizations. Use for "find orthopedic surgeons in Colorado", "orthopaedic surgeons in ZIP 80303", verifying a practice name, or listing a taxonomy in a city. Returns NPI, name, credential, taxonomies with state licenses, addresses and secondary practice locations.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name
limitNoMax results, 1-50 (default 10)
stateNoTwo-letter state code, e.g. CO
taxonomyNoSpecialty as NPPES words it, e.g. "Orthopaedic Surgery" (British spelling)
last_nameNoFamily name of an individual provider
first_nameNoGiven name of an individual provider
postal_codeNo5-digit US ZIP code (or ZIP+4). Matches practice-location addresses, including secondary practice locations
organizationNoOrganization name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It usefully describes return fields, including NPI, name, credential, taxonomies, addresses, and secondary practice locations, but it does not state whether the operation is read-only, whether authentication is required, or what the response structure looks like. For a search tool with no annotations, this adds some value but leaves meaningful behavioral gaps.

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?

The description is two sentences with the purpose front-loaded, followed by example use cases and a concise return summary. Every sentence serves a clear role, and there is no redundant or boilerplate wording.

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 an eight-parameter search tool with no required parameters, no annotations, and no output schema, the description covers the core purpose, example queries, and returned data fields well. It could go further by noting that all filters are optional or by clarifying result behavior such as the default/maximum limit, but the schema covers those mechanics and the description is otherwise complete enough for correct invocation.

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%, so the schema already documents all eight parameters, including the taxonomy spelling example and the postal_code matching behavior. The description mostly echoes those field meanings and adds no parameter-level guidance beyond what the schema supplies. The baseline of 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb and resource: search the CMS NPPES NPI registry for clinicians or organizations. It clearly distinguishes itself from retrieval-oriented siblings like get_provider by framing the tool as a search. The example queries reinforce the exact capability without ambiguity.

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?

The description gives clear usage context through concrete example queries such as 'find orthopedic surgeons in Colorado' and verifying a practice name. It does not explicitly name when to use get_provider or other alternatives, nor does it state exclusions, but the examples make the intended context unambiguous.

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.