Skip to main content
Glama

get_npi_provider_verification

Read-only

Use when verifying a clinician or organization NPI against CMS NPPES before contracting or credentialing. Returns enumeration status, taxonomy, license state, and identity fields from live NPPES lookup. Source: CMS NPPES Registry. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $1.00 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
npiNo
stateNo
provider_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured information: the lookup is live against NPPES, each call costs $1.00 USDC, and results carry a signed settlement receipt verifiable at a specific URL. It does not address failure modes such as an unmatched NPI or invalid format, which keeps it at 4.

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

Conciseness3/5

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

The usage condition and return fields are front-loaded and useful, but the closing two sentences about post-quantum attestation and the verification URL are promotional framing that consume space without helping an agent decide or call. The pricing sentence does earn its place.

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, so the description appropriately enumerates the returned fields (enumeration status, taxonomy, license state, identity fields). However, for a lookup tool with three unconstrained parameters it omits what happens on no-match and how the parameters combine, leaving real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and none of the three parameters (npi, state, provider_name) are explained in the description. It is unclear whether state and provider_name are optional filters, alternative lookup keys, or disambiguators, and with zero required parameters it is ambiguous whether an empty call is valid.

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 names a specific verb (verify) and resource (clinician or organization NPI) and identifies the authoritative source, CMS NPPES. It is clearly distinguishable from analytics siblings such as get_provider_market_intelligence because it performs a live registry lookup rather than producing derived intelligence.

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 opening phrase 'Use when verifying ... before contracting or credentialing' gives a concrete decision context for invoking the tool. It does not state exclusion cases or name an alternative tool for adjacent needs, so it falls short of a full 5.

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