Skip to main content
Glama

list_providers

Retrieve healthcare providers from your practice, filtering by name or specialty to find specific medical professionals.

Instructions

List all healthcare providers in the practice

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results
nameNoFilter by provider name
specialtyNoFilter by specialty

Implementation Reference

  • The handler function that implements the core logic of the 'list_providers' tool. It calls the AthenaHealthClient's getProviders method with the provided arguments and returns the providers list as JSON or an error response.
    async handleListProviders(args: any) {
      try {
        const providers = await this.client.getProviders(args);
    
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify(providers, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify({
                error: 'Failed to list providers',
                message: error.message || 'Unknown error occurred',
                details: error.details || error.message,
              }, null, 2),
            },
          ],
        };
      }
    }
  • The tool definition including name, description, and input schema for validating arguments to the 'list_providers' tool.
    {
      name: 'list_providers',
      description: 'List all healthcare providers in the practice',
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number', description: 'Maximum number of results', default: 50 },
          name: { type: 'string', description: 'Filter by provider name' },
          specialty: { type: 'string', description: 'Filter by specialty' },
        },
        required: [],
      },
    },
  • The switch case in the MCP server's tool call handler that registers and dispatches 'list_providers' calls to the appropriate ToolHandlers method.
    case 'list_providers':
      return await this.toolHandlers.handleListProviders(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't cover aspects like pagination, rate limits, authentication needs, or what 'all' entails (e.g., active only, includes archived). This leaves significant gaps for a tool with parameters.

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, direct sentence that efficiently conveys the core purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has parameters and no output schema, the description is too minimal. It doesn't explain return values, filtering behavior, or how parameters interact (e.g., if 'name' and 'specialty' are combined). With no annotations and incomplete behavioral context, it falls short for effective agent use.

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?

The input schema has 100% description coverage, fully documenting the three parameters (limit, name, specialty) with clear descriptions. The tool description adds no additional parameter information beyond what the schema provides, so it meets the baseline for high schema coverage.

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 clearly states the action ('List') and resource ('healthcare providers in the practice'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling tools like 'list_departments' or 'search_patients' that might also list entities, missing full differentiation.

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 'search_patients' or 'list_departments', nor does it mention any prerequisites or exclusions. It's a basic statement of function without contextual usage advice.

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/ophydami/Athenahealth-MCP'

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