Skip to main content
Glama
manolaz

Emergency Medicare Planner MCP Server

by manolaz

check_medicare_coverage

Verify Medicare coverage for specific treatments and procedures by entering the treatment code, state, and insurance type. Determine eligibility and plan for emergency medical needs effectively.

Instructions

Checks what treatments and procedures are covered by Medicare

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
insuranceTypeNoType of Medicare insurance (e.g., Part A, Part B)
stateYesUS State code (e.g., CA, NY)
treatmentCodeYesMedicare treatment or procedure code

Implementation Reference

  • Handler for the check_medicare_coverage tool: validates input schema and returns mock Medicare coverage information.
    case "check_medicare_coverage": {
      const validatedArgs = CheckMedicareCoverageSchema.parse(args);
      // Mock implementation - would connect to Medicare database in real implementation
      return {
        content: [
          {
            type: "text",
            text: `Medicare coverage for ${validatedArgs.treatmentCode} in ${validatedArgs.state}:\n` +
                  `Coverage Type: ${validatedArgs.insuranceType || "Standard"}\n` +
                  `Coverage Status: Covered\n` +
                  `Co-pay: $25\n` +
                  `Deductible: Applies\n` +
                  `Special Requirements: Prior authorization needed`,
          },
        ],
      };
    }
  • Zod schema defining the input parameters for the check_medicare_coverage tool.
    const CheckMedicareCoverageSchema = z.object({
      treatmentCode: z.string().describe("Medicare treatment or procedure code"),
      state: z.string().describe("US State code (e.g., CA, NY)"),
      insuranceType: z.string().optional().describe("Type of Medicare insurance (e.g., Part A, Part B)"),
    });
  • index.ts:269-273 (registration)
    Registration of the check_medicare_coverage tool in the ListToolsRequestHandler response.
    {
      name: "check_medicare_coverage",
      description: "Checks what treatments and procedures are covered by Medicare",
      inputSchema: zodToJsonSchema(CheckMedicareCoverageSchema),
    },
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 the tool 'Checks' coverage, implying a read-only operation, but doesn't specify whether it requires authentication, has rate limits, returns detailed or summary information, or handles errors. This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly and understand the core function.

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 complexity of checking Medicare coverage, the lack of annotations and output schema, and the description's minimal detail, it's incomplete. It doesn't explain what the return value includes (e.g., coverage details, limitations, or next steps), which is crucial for a tool with no output schema, leaving the agent uncertain about the result format.

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, clearly documenting all three parameters (insuranceType, state, treatmentCode) with their types and purposes. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score without compensating or enhancing the schema's information.

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 tool's purpose with a specific verb ('Checks') and resource ('what treatments and procedures are covered by Medicare'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'find_nearby_medical_facilities' or 'get_emergency_contacts', which serve different healthcare-related functions, so it doesn't reach the highest score.

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. It doesn't mention prerequisites, exclusions, or how it relates to sibling tools such as 'schedule_emergency_transport' or 'sequentialthinking', leaving the agent to infer usage context without explicit direction.

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

Related 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/manolaz/emergency-medicare-planner-mcp-server'

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