Skip to main content
Glama

get-directions

Calculate routes between two locations using driving, walking, bicycling, or transit modes to provide navigation guidance.

Instructions

Get directions between two locations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYesStarting location (address or lat,lng)
destinationYesEnding location (address or lat,lng)
modeNoTravel mode

Implementation Reference

  • Main handler function for get-directions tool that calls Google Maps Directions API, processes the route data, and formats the response using formatDirectionsToMarkdown.
    export async function getDirections(
      params: z.infer<typeof directionsSchema>,
      extra?: any
    ) {
      const apiKey = process.env.GOOGLE_MAPS_API_KEY;
      if (!apiKey) {
        throw new Error("GOOGLE_MAPS_API_KEY is required");
      }
    
      try {
        const response = await googleMapsClient.directions({
          params: {
            origin: params.origin,
            destination: params.destination,
            mode: (params.mode || "driving") as any,
            key: apiKey,
          },
        });
    
        const routes = response.data.routes;
        if (routes.length === 0) {
          return {
            content: [
              {
                type: "text" as const,
                text: "No routes found between the given locations.",
              },
            ],
          };
        }
    
        const route = routes[0];
        const leg = route.legs[0];
    
        const routeData = {
          distance: leg.distance.text,
          duration: leg.duration.text,
          start_address: leg.start_address,
          end_address: leg.end_address,
          steps: leg.steps.map((step) => ({
            instruction: step.html_instructions.replace(/<[^>]*>/g, ""),
            distance: step.distance.text,
            duration: step.duration.text,
          })),
        };
    
        return {
          content: [
            {
              type: "text" as const,
              text: formatDirectionsToMarkdown(routeData),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error getting directions: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod schema defining input parameters for the get-directions tool: origin, destination, and optional mode.
    export const directionsSchema = z.object({
      origin: z.string().describe("Starting location (address or lat,lng)"),
      destination: z.string().describe("Ending location (address or lat,lng)"),
      mode: z
        .enum(["driving", "walking", "bicycling", "transit"])
        .optional()
        .describe("Travel mode"),
    });
  • src/index.ts:90-97 (registration)
    Registration of the get-directions tool on the MCP server using server.tool, referencing directionsSchema and getDirections handler.
    server.tool(
      "get-directions",
      "Get directions between two locations",
      directionsSchema.shape,
      async (params) => {
        return await getDirections(params);
      }
    );
  • Helper function to format directions data into Markdown for the tool response.
    function formatDirectionsToMarkdown(route: any): string {
      let markdown = `# Directions: ${route.start_address} → ${route.end_address}\n\n`;
      markdown += `Distance: ${route.distance}  \n`;
      markdown += `Duration: ${route.duration}  \n\n`;
      
      if (route.steps && route.steps.length) {
        markdown += `## Step-by-Step Directions\n\n`;
        route.steps.forEach((step: any, index: number) => {
          markdown += `${index + 1}. ${step.instruction} *(${step.distance}, ${step.duration})*\n`;
        });
      }
      
      return markdown;
    }
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. 'Get directions' implies a read-only operation, but it doesn't mention rate limits, authentication requirements, response format, or whether this is a real-time or cached service. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 communicates the core purpose without any wasted words. It's appropriately sized for a straightforward tool and gets directly to the point.

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 directions tool with no annotations and no output schema, the description is inadequate. It doesn't explain what kind of directions are returned (step-by-step, summary, ETA), whether multiple routes are provided, or any limitations. The agent would need to guess about the output format and behavioral characteristics.

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 description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Get' and resource 'directions between two locations', making the purpose immediately understandable. It doesn't differentiate from siblings like 'distance-matrix' or 'geocode', but it's specific enough to understand what the tool does.

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 'distance-matrix' or 'geocode'. It doesn't mention prerequisites, constraints, or typical use cases, leaving the agent to infer usage context from the tool name alone.

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/CaptainCrouton89/maps-mcp'

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