Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__get_provider

Fetch a provider by 10-digit NPI.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "npi": "1234567890"
    },
    "name": "npi-registry__get_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiYes10-digit NPI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses almost nothing. It does not state the failure behavior when an NPI is unregistered (empty result vs. error), whether the NPI is validated or normalized, whether the response is a full provider record, or whether any auth/quota applies. "Fetch" weakly implies a read-only operation but that is inference, not disclosure.

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?

A single front-loaded sentence with zero filler; the identifier constraint is stated up front. It is arguably over-trimmed rather than verbose, but nothing in it is wasted.

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?

The tool is simple (one required string parameter, no nesting) and there is no output schema, so the description need not enumerate return fields. However, for a lookup tool whose whole value is the returned provider record, the absence of any statement about what comes back or what happens on a miss leaves a real gap.

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% and the single parameter already carries the description "10-digit NPI", which is essentially identical to the description's wording. The description adds no format, validation, or example semantics beyond the schema, so the 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 states a specific verb and resource ("Fetch a provider") and the key identifier (10-digit NPI), so the agent knows exactly what the call returns conceptually. It does not distinguish this lookup from the sibling npi_registry_search, which is the obvious alternative for anything short of an exact NPI match.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says to prefer this over npi_registry_search when you have a full NPI, and nothing says what to do when you only have a name or partial identifier. The agent must infer the exact-match precondition from the phrase "10-digit NPI" alone.

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.