Skip to main content
Glama
mapbox

Mapbox MCP Server

Official
by mapbox
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Matrix Tool

matrix_tool
Read-onlyIdempotent

Calculate travel times and distances between multiple points with the Mapbox Matrix API. Supports driving, walking, and cycling profiles.

Instructions

Calculates travel times and distances between multiple points using Mapbox Matrix API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileYesRouting profile for different modes of transport. Options: - mapbox/driving-traffic (default): automotive with current traffic conditions (limited to 10 coordinates) - mapbox/driving: automotive based on typical traffic - mapbox/walking: pedestrian/hiking - mapbox/cycling: bicycle
sourcesNoUse the coordinates at given indices as sources. Possible values are: a semicolon-separated list of 0-based indices, or "all" (default). The option "all" allows using all coordinates as sources.
bearingsNoA semicolon-separated list of headings and allowed deviation indicating the direction of movement. Input as two comma-separated values per location: a heading course measured clockwise from true north between 0 and 360, and the range of degrees by which the angle can deviate (recommended value is 45° or 90°), formatted as {angle,degrees}. If provided, the number of bearings must equal the number of coordinates. You can skip a coordinate and show its position in the list with the ; separator.
approachesNoA semicolon-separated list indicating the side of the road from which to approach waypoints. Accepts "unrestricted" (default, route can arrive at the waypoint from either side of the road) or "curb" (route will arrive at the waypoint on the driving_side of the region). If provided, the number of approaches must be the same as the number of waypoints. You can skip a coordinate and show its position with the ; separator.
annotationsNoSpecifies the resulting matrices. Possible values are: duration (default), distance, or both values separated by a comma.
coordinatesYesArray of coordinate objects with longitude and latitude properties. Must include at least 2 coordinate pairs. Up to 25 coordinates total are supported for most profiles (10 for driving-traffic).
destinationsNoUse the coordinates at given indices as destinations. Possible values are: a semicolon-separated list of 0-based indices, or "all" (default). The option "all" allows using all coordinates as destinations.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
messageNo
sourcesYes
distancesNo
durationsNo
destinationsYes

Tool Definition Quality

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds only the API source (Mapbox Matrix) but no additional behavioral context (e.g., API limits, pricing, or error handling). It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words. However, it could be slightly more structured with additional context, but it is appropriately brief for a straightforward tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 parameters, output schema exists, many siblings) the description is minimal. It does not explain return values but output schema covers that. Still, it misses nuances like coordinate limits or profile constraints already in schema, so overall adequate but not thorough.

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 baseline is 3. The description adds no parameter-specific details beyond what the schema already provides, so it meets the baseline without improvement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Calculates' and the resource 'travel times and distances between multiple points using Mapbox Matrix API'. It distinguishes from siblings like directions_tool (point-to-point) by emphasizing 'multiple points' (matrix computation).

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 directions_tool or distance_tool. It lacks explicit when-not-to-use or alternative suggestions, which is a significant gap given the many sibling tools.

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/mapbox/mcp-server'

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