Skip to main content
Glama

CMS Medicare Doctors and Clinicians file: clinician NPI

health_physician_compare_cms
Read-only

CMS Medicare Doctors and Clinicians file: clinician NPI, name, credential, specialty, medical school, graduation year and practice location, by last name and optional state. Hospital affiliations are not in this file (only the practice group name). Up to 20 records per call. 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

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": {
      "last_name": "<last_name>"
    },
    "name": "health_physician_compare_cms"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many records, 1 to 20 (default 5)
stateNoTwo-letter state code, optional
last_nameYesClinician last name, letters, spaces, apostrophes and hyphens, 2 to 60 characters

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the result cap ('Up to 20 records per call'), the exact price ($0.002 per successful call), the payment rail (x402 / USDC on Base, Solana and 10 more networks), and the billing policy that failed calls are free. These are material behavioral facts an agent cannot get from annotations or 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 dense sentences: dataset scope first, exclusion second, limits and pricing last. No filler, and the constraint most likely to surprise an agent (cost and result cap) is stated plainly rather than buried.

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-parameter lookup with an output schema and read-only annotations, the description covers everything needed to call it correctly: the key, the optional filter, the record ceiling, the field coverage gap, and the cost model. Return-value documentation is rightly delegated to the output schema.

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%, so the schema already documents all three parameters including the 1-20 range and the two-letter state format. The description only echoes 'last name and optional state' and the 20-record ceiling, adding little meaning beyond the structured fields; baseline 3 applies.

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 names the specific dataset (CMS Medicare Doctors and Clinicians), the entity (clinician NPI) and the exact fields returned, plus the lookup key ('by last name and optional state'). It also carves out an exclusion ('Hospital affiliations are not in this file'), which helps separate it from hospital-oriented siblings, though no sibling is named directly.

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?

Usage is clearly implied by 'by last name and optional state' and reinforced by the negative guidance that hospital affiliations are unavailable here (only the practice group name). What's missing is an explicit pointer to the alternative tool when an agent actually needs hospital affiliation data.

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