Skip to main content
Glama
manolaz

Emergency Medicare Planner MCP Server

by manolaz

get_emergency_contacts

Retrieve emergency contact details for a specific location using the Emergency Medicare Planner MCP Server. Specify location and service types to access relevant emergency services.

Instructions

Retrieves emergency contact information for a specific location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYesLocation to get emergency contacts for
serviceTypeNoTypes of emergency services needed

Implementation Reference

  • Handler function that validates input using GetEmergencyContactsSchema and returns mock emergency contact information including 911, nearest hospital, poison control, and Medicare hotline.
    case "get_emergency_contacts": {
      const validatedArgs = GetEmergencyContactsSchema.parse(args);
      return {
        content: [
          {
            type: "text",
            text: `Emergency contacts for ${validatedArgs.location}:\n` +
                  `Emergency Services: 911\n` +
                  `Nearest Hospital: General Hospital - (555) 123-4567\n` +
                  `Poison Control: (800) 222-1222\n` +
                  `Medicare Hotline: 1-800-MEDICARE`,
          },
        ],
      };
    }
  • Zod schema defining input for get_emergency_contacts tool: location (string) and optional serviceType (array of strings).
    const GetEmergencyContactsSchema = z.object({
      location: z.string().describe("Location to get emergency contacts for"),
      serviceType: z.array(z.string()).optional().describe("Types of emergency services needed"),
    });
  • index.ts:274-278 (registration)
    Registration of the get_emergency_contacts tool in the ListToolsRequestHandler response, including name, description, and input schema.
    {
      name: "get_emergency_contacts",
      description: "Retrieves emergency contact information for a specific location",
      inputSchema: zodToJsonSchema(GetEmergencyContactsSchema),
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Retrieves', implying a read-only operation, but doesn't cover aspects like authentication needs, rate limits, error handling, or what the return format looks like. This leaves significant gaps for a tool with no annotation coverage.

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 any redundant or unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent 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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the retrieved information includes, how it's formatted, or any behavioral traits like permissions or limitations. For a tool with no structured support, this leaves the agent under-informed.

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 schema description coverage is 100%, with clear descriptions for both parameters ('location' and 'serviceType'), so the schema does the heavy lifting. The description adds no additional semantic context beyond implying the parameters are used for filtering, which aligns with the schema but doesn't provide extra value.

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 verb ('Retrieves') and resource ('emergency contact information') with a specific scope ('for a specific location'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'find_nearby_medical_facilities' or 'schedule_emergency_transport', which might also involve emergency services, 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 such as the sibling tools. It mentions 'specific location' but doesn't specify prerequisites, exclusions, or contexts where this tool is preferred over others, leaving the agent with minimal usage 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