Skip to main content
Glama

SolvingHealth federal health data

get_provider

Look up one provider by 10-digit NPI. Use to verify an NPI is real, active, and matches the specialty you expect.

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": {
      "npi": "<npi>"
    },
    "name": "get_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiYesThe 10-digit NPI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose useful behavior beyond the name, namely that the result reveals validity, active status, and specialty, implying a read-only lookup, but it says nothing about permissions, rate limits, or what is returned when the NPI does not exist.

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?

Two short sentences with the identifier requirement and the verification purpose front-loaded; nothing is redundant or padded.

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 a one-parameter lookup with no output schema, the description covers the essential intent and the key field semantics. Only the not-found behavior is left unstated, which is a minor gap at this complexity level.

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 single npi parameter is already documented as "The 10-digit NPI." The description restates the 10-digit format but adds no parsing rules, alternate identifier acceptance, or validation behavior, so the schema does all the work.

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?

States a specific verb and resource ("Look up one provider") plus the identifier type (10-digit NPI), which cleanly separates a single-record fetch from the list-oriented find_providers sibling. It stops short of naming the alternative, but "one provider" makes the singular scope unambiguous.

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 a concrete use case: verify an NPI is real, active, and matches expected specialty, which tells the agent this is for validation rather than discovery. It does not explicitly say to use find_providers when the NPI is unknown, so the exclusion is implied rather than stated.

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.