Skip to main content
Glama
manolaz

Emergency Medicare Planner MCP Server

by manolaz

schedule_emergency_transport

Arrange emergency medical transport by specifying patient location, medical condition, and urgency level. Connects with medical facilities for efficient patient transfer.

Instructions

Arranges emergency medical transportation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destinationNoDestination hospital or clinic
medicalConditionYesBrief description of medical condition
patientLocationYesPatient's current location
urgencyYesLevel of urgency

Implementation Reference

  • Handler function for schedule_emergency_transport tool. Validates input args using the schema and returns a formatted response simulating emergency transport scheduling with details like ETA and transport ID.
    case "schedule_emergency_transport": {
      const validatedArgs = ScheduleEmergencyTransportSchema.parse(args);
      return {
        content: [
          {
            type: "text",
            text: `Emergency transport scheduled from ${validatedArgs.patientLocation}\n` +
                  `${validatedArgs.destination ? `To: ${validatedArgs.destination}\n` : ''}` +
                  `Urgency: ${validatedArgs.urgency}\n` +
                  `Condition: ${validatedArgs.medicalCondition}\n` +
                  `ETA: 12 minutes\n` +
                  `Transport ID: EMT-${Math.floor(Math.random() * 10000)}\n` +
                  `Please stand by and keep patient stable.`,
          },
        ],
      };
    }
  • Zod schema defining the input structure for the schedule_emergency_transport tool, including patient location, optional destination, medical condition, and urgency level.
    const ScheduleEmergencyTransportSchema = z.object({
      patientLocation: z.string().describe("Patient's current location"),
      destination: z.string().optional().describe("Destination hospital or clinic"),
      medicalCondition: z.string().describe("Brief description of medical condition"),
      urgency: z.enum(["critical", "urgent", "standard"]).describe("Level of urgency"),
    });
  • index.ts:279-283 (registration)
    Tool registration in the ListToolsRequestSchema handler, providing the tool's name, description, and converted JSON schema for MCP protocol compliance.
    {
      name: "schedule_emergency_transport",
      description: "Arranges emergency medical transportation",
      inputSchema: zodToJsonSchema(ScheduleEmergencyTransportSchema),
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Arranges' implies a write/mutation operation, but the description doesn't specify whether this triggers actual transportation, requires authorization, has side effects, or what happens after arrangement. This is inadequate for a tool that appears to perform a critical action.

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 states the core purpose without unnecessary words. It's appropriately sized for a tool with clear parameters documented elsewhere.

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?

For a tool that appears to perform a critical emergency action with no annotations and no output schema, the description is insufficient. It doesn't explain what 'arranges' means operationally, what confirmation or response to expect, or any constraints or requirements beyond the basic parameters documented in the schema.

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, so all parameters are documented in the schema itself. The description doesn't add any parameter-specific information beyond what's already in the schema descriptions. This meets the baseline expectation when schema coverage is complete.

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 ('arranges') and resource ('emergency medical transportation'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling tools like 'check_medicare_coverage' or 'find_nearby_medical_facilities' that might also relate to emergency medical services.

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. There's no mention of prerequisites, constraints, or how it differs from sibling tools like 'get_emergency_contacts' or 'sequentialthinking' that might be relevant in emergency medical situations.

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