Skip to main content
Glama

provider_enrich

Retrieve comprehensive provider intelligence, including practice details, specialties, affiliations, and market context, by inputting a 10-digit NPI number.

Instructions

AI-enriched provider intelligence from NPI number. Returns practice details, specialties, affiliations, and market context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
npiYes10-digit NPI number

Implementation Reference

  • Tool definition for 'provider_enrich' including name, description, price ($0.05), endpoint (/agent/v1/providers/enrich), and Zod schema requiring a 10-digit NPI number.
    {
      name: 'provider_enrich',
      description: 'AI-enriched provider intelligence from NPI number. Returns practice details, specialties, affiliations, and market context.',
      price: '$0.05',
      endpoint: '/agent/v1/providers/enrich',
      schema: {
        npi: z.string().describe('10-digit NPI number'),
      },
    },
  • src/index.js:17-62 (registration)
    Generic tool registration loop (s.tool()) that registers all tools from MCP_TOOLS including 'provider_enrich'. The handler proxies requests to the external API endpoint.
    function createMcpServer() {
      const s = new McpServer({ name: 'mymedi-ai', version: '1.2.1' });
      for (const tool of MCP_TOOLS) {
        s.tool(tool.name, tool.description, tool.schema, async (params) => {
          const toolDef = getToolByName(tool.name);
          if (!toolDef) {
            return { content: [{ type: 'text', text: `Unknown tool: ${tool.name}` }], isError: true };
          }
          try {
            const response = await fetch(`${API_BASE_URL}${toolDef.endpoint}`, {
              method: 'POST',
              headers: {
                'Content-Type': 'application/json',
                ...(API_KEY && { 'X-API-Key': API_KEY }),
                'X-Agent-ID': 'mcp-client',
                'User-Agent': '@mymedi-ai/mcp-server/1.2.1',
              },
              body: JSON.stringify(params),
            });
            if (response.status === 402) {
              const paymentInfo = await response.json();
              return {
                content: [{ type: 'text', text: JSON.stringify({
                  error: 'payment_required',
                  message: `This tool costs ${toolDef.price} per call. Register at ${API_BASE_URL}/bot-marketplace/register for an API key with 10 free starter credits, or pay per call with on-chain USDC (no signup) via the x402 protocol.`,
                  price: toolDef.price, register: `${API_BASE_URL}/bot-marketplace/register`, ...paymentInfo,
                }, null, 2) }], isError: true,
              };
            }
            if (!response.ok) {
              const error = await response.json().catch(() => ({ message: response.statusText }));
              return { content: [{ type: 'text', text: JSON.stringify({ error: true, status: response.status, ...error }, null, 2) }], isError: true };
            }
            const data = await response.json();
            const creditsSpent = response.headers.get('X-Credits-Spent');
            const creditsRemaining = response.headers.get('X-Credits-Remaining');
            if (creditsSpent) {
              data._billing = { creditsSpent: parseInt(creditsSpent, 10), creditsRemaining: creditsRemaining ? parseInt(creditsRemaining, 10) : undefined, priceUSD: toolDef.price };
            }
            return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
          } catch (err) {
            return { content: [{ type: 'text', text: JSON.stringify({ error: true, message: err.message, hint: 'Ensure MCP_API_BASE_URL and MCP_API_KEY environment variables are set.' }, null, 2) }], isError: true };
          }
        });
      }
      return s;
  • Generic async handler for all tools including 'provider_enrich'. Calls the external REST API at /agent/v1/providers/enrich with the npi parameter, handles 402 payment responses, error responses, and billing headers.
    s.tool(tool.name, tool.description, tool.schema, async (params) => {
      const toolDef = getToolByName(tool.name);
      if (!toolDef) {
        return { content: [{ type: 'text', text: `Unknown tool: ${tool.name}` }], isError: true };
      }
      try {
        const response = await fetch(`${API_BASE_URL}${toolDef.endpoint}`, {
          method: 'POST',
          headers: {
            'Content-Type': 'application/json',
            ...(API_KEY && { 'X-API-Key': API_KEY }),
            'X-Agent-ID': 'mcp-client',
            'User-Agent': '@mymedi-ai/mcp-server/1.2.1',
          },
          body: JSON.stringify(params),
        });
        if (response.status === 402) {
          const paymentInfo = await response.json();
          return {
            content: [{ type: 'text', text: JSON.stringify({
              error: 'payment_required',
              message: `This tool costs ${toolDef.price} per call. Register at ${API_BASE_URL}/bot-marketplace/register for an API key with 10 free starter credits, or pay per call with on-chain USDC (no signup) via the x402 protocol.`,
              price: toolDef.price, register: `${API_BASE_URL}/bot-marketplace/register`, ...paymentInfo,
            }, null, 2) }], isError: true,
          };
        }
        if (!response.ok) {
          const error = await response.json().catch(() => ({ message: response.statusText }));
          return { content: [{ type: 'text', text: JSON.stringify({ error: true, status: response.status, ...error }, null, 2) }], isError: true };
        }
        const data = await response.json();
        const creditsSpent = response.headers.get('X-Credits-Spent');
        const creditsRemaining = response.headers.get('X-Credits-Remaining');
        if (creditsSpent) {
          data._billing = { creditsSpent: parseInt(creditsSpent, 10), creditsRemaining: creditsRemaining ? parseInt(creditsRemaining, 10) : undefined, priceUSD: toolDef.price };
        }
        return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
      } catch (err) {
        return { content: [{ type: 'text', text: JSON.stringify({ error: true, message: err.message, hint: 'Ensure MCP_API_BASE_URL and MCP_API_KEY environment variables are set.' }, null, 2) }], isError: true };
      }
    });
  • getToolByName helper function that looks up a tool definition by name from the MCP_TOOLS array.
    export function getToolByName(name) {
      return MCP_TOOLS.find((t) => t.name === name);
    }
Behavior2/5

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

No annotations provided; description does not disclose side effects, authentication, rate limits, or whether results are cached. 'AI-enriched' implies processing but no further detail.

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 concise sentences front-load core purpose. No superfluous text.

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?

Though no output schema, description lists key return categories (practice details, specialties, etc.). For a single-parameter tool, this is fairly complete.

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% with clear parameter description. Description adds no semantic depth beyond the schema. Baseline of 3 is appropriate.

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?

Clearly states it takes an NPI number and returns enriched provider data (practice details, specialties, affiliations, market context). Distinct from sibling tools like provider_search and provider_payments.

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 explicit guidance on when to use this tool vs alternatives such as provider_search. Does not specify prerequisites or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MyMedi-AI/mymedi-ai-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server