Skip to main content
Glama

distance-matrix

Calculate travel distance and time between multiple origins and destinations using driving, walking, bicycling, or transit modes.

Instructions

Calculate travel distance and time between multiple origins and destinations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originsYesArray of origin locations
destinationsYesArray of destination locations
modeNoTravel mode

Implementation Reference

  • The distanceMatrix function implements the core logic for the 'distance-matrix' tool using Google Maps Distance Matrix API, processes origins and destinations, formats results into markdown, and handles errors.
    export async function distanceMatrix(
      params: z.infer<typeof distanceMatrixSchema>,
      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.distancematrix({
          params: {
            origins: params.origins,
            destinations: params.destinations,
            mode: (params.mode || "driving") as any,
            key: apiKey,
          },
        });
    
        const rows = response.data.rows;
        const results = [];
    
        for (let i = 0; i < params.origins.length; i++) {
          for (let j = 0; j < params.destinations.length; j++) {
            const element = rows[i].elements[j];
            results.push({
              origin: params.origins[i],
              destination: params.destinations[j],
              distance: element.distance?.text || "N/A",
              duration: element.duration?.text || "N/A",
              status: element.status,
            });
          }
        }
    
        return {
          content: [
            {
              type: "text" as const,
              text: formatDistanceMatrixToMarkdown(results),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error calculating distance matrix: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters for the distance-matrix tool: origins, destinations arrays, and optional mode.
    export const distanceMatrixSchema = z.object({
      origins: z.array(z.string()).describe("Array of origin locations"),
      destinations: z.array(z.string()).describe("Array of destination locations"),
      mode: z
        .enum(["driving", "walking", "bicycling", "transit"])
        .optional()
        .describe("Travel mode"),
    });
  • src/index.ts:100-107 (registration)
    Registration of the 'distance-matrix' tool on the MCP server, linking to the handler and schema.
    server.tool(
      "distance-matrix",
      "Calculate travel distance and time between multiple origins and destinations",
      distanceMatrixSchema.shape,
      async (params) => {
        return await distanceMatrix(params);
      }
    );
  • Helper function to format distance matrix results into readable Markdown.
    function formatDistanceMatrixToMarkdown(results: any[]): string {
      let markdown = `# Distance Matrix Results\n\n`;
      
      results.forEach((result, index) => {
        markdown += `## ${index + 1}. ${result.origin} → ${result.destination}\n`;
        markdown += `Distance: ${result.distance}  \n`;
        markdown += `Duration: ${result.duration}  \n`;
        markdown += `Status: ${result.status}  \n\n`;
      });
      
      return markdown;
    }
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 mentions 'calculate' but doesn't specify whether this is a read-only operation, requires API keys, has rate limits, or returns structured data. For a tool with no annotation coverage, this is a significant gap in transparency.

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 front-loads the core functionality without any wasted words. It's appropriately sized for the tool's complexity, making it easy to parse and understand 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 no annotations and no output schema, the description is incomplete for a tool with 3 parameters and computational complexity. It doesn't explain return values, error handling, or behavioral traits like authentication needs, which are crucial for an AI agent to use it correctly.

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 description adds minimal meaning beyond the input schema, which has 100% coverage and includes descriptions for all parameters. It implies the tool handles arrays of locations but doesn't elaborate on format (e.g., addresses, coordinates) or constraints. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding.

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 specific verbs ('calculate travel distance and time') and resources ('between multiple origins and destinations'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-directions' or 'geocode', which might offer related functionality, 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 'get-directions' for point-to-point routes or 'geocode' for location conversion. It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage from the purpose 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