Skip to main content
Glama

market_analysis

Analyze healthcare specialty market in a US state. Obtain provider density, competition metrics, and market opportunity data.

Instructions

Healthcare specialty market analysis for a specific state. Returns provider density, competition metrics, and market opportunity data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYes2-letter state code (e.g., "TX", "CA")
specialtyYesMedical specialty (e.g., "cardiology", "orthopedics")

Implementation Reference

  • Tool definition for market_analysis: registers the tool with description, price ($0.10), endpoint (/agent/v1/market/analysis), and Zod schema (state + specialty inputs).
    {
      name: 'market_analysis',
      description: 'Healthcare specialty market analysis for a specific state. Returns provider density, competition metrics, and market opportunity data.',
      price: '$0.10',
      endpoint: '/agent/v1/market/analysis',
      schema: {
        state: z.string().describe('2-letter state code (e.g., "TX", "CA")'),
        specialty: z.string().describe('Medical specialty (e.g., "cardiology", "orthopedics")'),
      },
    },
  • Input schema for market_analysis: requires 'state' (2-letter code) and 'specialty' (medical specialty name).
      endpoint: '/agent/v1/market/analysis',
      schema: {
        state: z.string().describe('2-letter state code (e.g., "TX", "CA")'),
        specialty: z.string().describe('Medical specialty (e.g., "cardiology", "orthopedics")'),
      },
    },
  • src/index.js:20-61 (registration)
    Generic tool registration loop in createMcpServer(): iterates all MCP_TOOLS (including market_analysis) and registers each with the McpServer via s.tool(). The handler fetches from the tool's endpoint URL with the params as JSON body.
      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 };
        }
      });
    }
  • src/index.js:69-71 (registration)
    Sandbox registration in createSandboxServer(): also registers market_analysis but returns a static 'sandbox' response instead of calling the live API.
      sandboxServer.tool(tool.name, tool.description, tool.schema,
        async () => ({ content: [{ type: 'text', text: 'sandbox' }] }));
    }
Behavior2/5

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

Without annotations, the description carries full burden for behavioral disclosure. It only lists return data types but does not specify if the tool is read-only, any side effects, data freshness, or authorization requirements. This is insufficient for an agent to understand operational constraints.

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 sentence, front-loaded with the purpose, and includes the key return items. No unnecessary words.

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 simple tool with two required params and no output schema, the description provides adequate high-level context but lacks detail on return format, data sources, or limits. It could briefly note if results are aggregated or raw.

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 descriptions for both parameters (state code and specialty). The description adds no new insight beyond restating 'for a specific state', so it meets but does not exceed the baseline expected given schema completeness.

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 tool performs healthcare specialty market analysis for a specific state, returning provider density, competition metrics, and market opportunity data. This verb+resource combination distinguishes it from sibling tools like provider_enrich or provider_search which focus on individual providers.

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?

The description provides no guidance on when to use this tool versus alternatives like provider_enrich or claims_validate. It does not mention any when-not-to-use scenarios or prerequisites.

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