Skip to main content
Glama
mymedi-ai-mcp-server

mymedi-ai-mcp-server

by MyMedi-AI

NPI provider directory search

provider_search
Read-only

Search the NPI provider directory to find healthcare providers by name, specialty, or location.

Instructions

Search the NPI provider directory. Find healthcare providers by name, specialty, or location.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNoMax results (default 10, max 50)
stateNo2-letter state code
lastNameNo
taxonomyNoProvider specialty as an NPPES (NUCC) taxonomy description, e.g. "Family Medicine"; a trailing * matches a prefix
firstNameNo
organizationNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.7.9
    • addedInput schema / properties / city / maxLength
      Added value: +500
    • addedInput schema / properties / firstName / maxLength
      Added value: +100
    • addedInput schema / properties / lastName / maxLength
      Added value: +100
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / organizationName / maxLength
      Added value: +100
    • addedInput schema / properties / state / maxLength
      Added value: +500
    • changedInput schema / properties / taxonomy / description
      Previous value: -"Provider taxonomy/specialty code"New value: +"Provider specialty as an NPPES (NUCC) taxonomy description, e.g. \"Family Medicine\"; a trailing * matches a prefix"
    • addedInput schema / properties / taxonomy / maxLength
      Added value: +500
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare this as a read-only, open-world, non-destructive search, so the safety profile is covered. The description adds that the data source is the NPI provider directory, but does not disclose result limits, ordering, authentication needs, or other search behavior beyond the general field categories.

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, front-loaded with the core action and followed by the supported search dimensions. There is no filler or repetition.

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?

For a seven-parameter, all-optional read-only search, the description is adequate but thin. It omits routing guidance versus provider_enrich and does not clarify whether at least one search field is expected, leaving some operational uncertainty despite the annotations and schema covering the rest.

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 only 43%, so the description must add meaning. It partially compensates by grouping searches into name, specialty, and location, which maps conceptually to the undocumented name and city parameters, but it does not clarify all optional combinations or the limit parameter beyond what the schema already states.

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: search the NPI provider directory, and clarifies the searchable dimensions (name, specialty, location). It is clear against a generic tool list, but does not explicitly distinguish itself from sibling tools such as provider_enrich.

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

Usage Guidelines3/5

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

The description implies usage by saying it finds healthcare providers by name, specialty, or location, but it gives no explicit when-to-use guidance, prerequisites, or exclusions. It also does not tell the agent when to prefer provider_search over provider_enrich or other provider-related siblings.

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