Skip to main content
Glama

Npi Registry

by io.github.pipeworx-io

Get Provider

get_provider
Read-onlyIdempotent

Fetch a provider by 10-digit NPI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
npiYes10-digit NPI

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ErrorsNoAPI error messages if any
resultsNoArray containing single provider record
result_countNoTotal number of results (0 or 1)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed16 schema fields changed
    • changedOutput schema / properties / Errors / description
      Previous value: -"Any errors encountered"New value: +"API error messages if any"
    • addedOutput schema / properties / Errors / items
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / result_count / description
      Previous value: -"Number of results (0 if NPI not found, 1 if found)"New value: +"Total number of results (0 or 1)"
    • changedOutput schema / properties / result_count / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / results / description
      Previous value: -"Array containing the single provider record (empty if NPI not found)"New value: +"Array containing single provider record"
    • changedOutput schema / properties / results / items / properties / addresses / description
      Previous value: -"Provider addresses"New value: +"Provider address records"
    • addedOutput schema / properties / results / items / properties / addresses / items
      Added value: +{
+  "properties": {
+    "address_1": {
+      "type": "string"
+    },
+    "address_2": {
+      "type": "string"
+    },
+    "address_purpose": {
+      "type": "string"
+    },
+    "address_type": {
+      "type": "string"
+    },
+    "city": {
+      "type": "string"
+    },
+    "country_code": {
+      "type": "string"
+    },
+    "postal_code": {
+      "type": "string"
+    },
+    "state": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / results / items / properties / basic / properties
      Added value: +{
+  "credential_text": {
+    "type": "string"
+  },
+  "first_name": {
+    "type": "string"
+  },
+  "last_name": {
+    "type": "string"
+  },
+  "organization_name": {
+    "type": "string"
+  }
+}
    • removedOutput schema / properties / results / items / properties / endpoints
      Removed value: -{
-  "description": "FHIR/electronic endpoints",
-  "type": "array"
-}
    • addedOutput schema / properties / results / items / properties / enumeration_type
      Added value: +{
+  "description": "NPI-1 (individual) or NPI-2 (organization)",
+  "type": "string"
+}
    • removedOutput schema / properties / results / items / properties / identifiers
      Removed value: -{
-  "description": "Secondary identifiers",
-  "type": "array"
-}
    • changedOutput schema / properties / results / items / properties / number / description
      Previous value: -"10-digit NPI"New value: +"10-digit NPI identifier"
    • removedOutput schema / properties / results / items / properties / practitioner_codes
      Removed value: -{
-  "description": "Practitioner codes",
-  "type": "array"
-}
    • changedOutput schema / properties / results / items / properties / taxonomies / description
      Previous value: -"Provider taxonomies (specialties)"New value: +"Provider taxonomy specializations"
    • addedOutput schema / properties / results / items / properties / taxonomies / items
      Added value: +{
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "primary": {
+      "type": "boolean"
+    },
+    "taxonomy_description": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedOutput schema / properties / results / items / properties / type
      Removed value: -{
-  "description": "Provider type (NPI-1 for individual, NPI-2 for organization)",
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "npi": "1234567890"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "Errors": {
+      "description": "Any errors encountered",
+      "type": "array"
+    },
+    "result_count": {
+      "description": "Number of results (0 if NPI not found, 1 if found)",
+      "type": "integer"
+    },
+    "results": {
+      "description": "Array containing the single provider record (empty if NPI not found)",
+      "items": {
+        "properties": {
+          "addresses": {
+            "description": "Provider addresses",
+            "type": "array"
+          },
+          "basic": {
+            "description": "Basic provider information",
+            "type": "object"
+          },
+          "endpoints": {
+            "description": "FHIR/electronic endpoints",
+            "type": "array"
+          },
+          "identifiers": {
+            "description": "Secondary identifiers",
+            "type": "array"
+          },
+          "number": {
+            "description": "10-digit NPI",
+            "type": "string"
+          },
+          "practitioner_codes": {
+            "description": "Practitioner codes",
+            "type": "array"
+          },
+          "taxonomies": {
+            "description": "Provider taxonomies (specialties)",
+            "type": "array"
+          },
+          "type": {
+            "description": "Provider type (NPI-1 for individual, NPI-2 for organization)",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds no behavioral context (e.g., response format, performance) beyond what annotations provide. A score of 3 reflects adequate but not enhanced transparency given annotation presence.

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 a single, concise sentence that immediately conveys the core purpose. No extraneous information; every word earns its place.

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?

Given the tool's simplicity (single parameter), presence of output schema, and thorough annotations, the description suffices. It covers what the tool does and the key constraint. Minor improvement could mention that it returns a full provider object, but output schema handles that.

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%: the input schema already describes the 'npi' parameter as '10-digit NPI'. The tool description repeats this without adding further details (e.g., format or validation rules). Thus, no additional semantic value beyond schema.

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 clearly states the action ('Fetch') and the specific resource ('provider by 10-digit NPI'), including a precise constraint (10-digit). This distinguishes it from sibling tools like 'entity_profile' that might retrieve provider info by other means.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that this is the tool for NPI-based lookups or that 'entity_profile' might be used for other identifiers. The agent receives no help in disambiguating tool choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Npi Registry toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

The tools are generally distinct, with clear purposes for NPI registry operations, but some overlap exists between ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded, which all route to the same underlying data but with different response modes. Additionally, bet_research and polymarket_edges both offer analysis of prediction markets, causing potential confusion.

Naming Consistency3/5

The naming is mixed: some tools follow a consistent verb_noun pattern (e.g., search, remember, forget), while others use descriptive but non-pattern names like ai_visibility_check or ask_pipeworx_grounded. There is also a mix of snake_case and camelCase (e.g., generate_llms_txt vs. ai_visibility_check).

Tool Count4/5

With 33 tools, the count is slightly high but still reasonable given the broad scope of the server, which covers NPI registry, company profiles, prediction markets, AI visibility, and more. Each tool serves a distinct purpose, though a few could potentially be consolidated.

Completeness3/5

The tool surface covers the NPI registry core (search, get by NPI) but lacks obvious CRUD operations like create, update, or delete for providers. For other domains like company profiles, it has good coverage, but the NPI-specific functionality feels incomplete without lifecycle management.

Resources