Skip to main content
Glama
mapbox

Mapbox MCP Server

Official

Isochrone Tool

isochrone_tool
Read-onlyIdempotent

Compute areas reachable within a given travel time or distance from a coordinate. Returns GeoJSON contours for displaying travel ranges by mode.

Instructions

Computes areas that are reachable within a specified amount of time from a location, and returns the reachable regions as contours of Polygons or LineStrings in GeoJSON format that you can display on a map. Common use cases: - Show a user how far they can travel in X minutes from their current location - Determine whether a destination is within a certain travel time threshold - Compare travel ranges for different modes of transportation'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
denoiseNoA floating point value that can be used to remove smaller contours. A value of 1.0 will only return the largest contour for a given value.
excludeNoExclude certain road types and custom locations from routing.
profileNoMode of travel.mapbox/driving-traffic
polygonsNoWhether to return Polygons (true) or LineStrings (false).
depart_atNoAn ISO 8601 date-time string representing the time to depart (format string: YYYY-MM-DDThh:mmss±hh:mm).
generalizeYesPositive number in meters that is used to simplify geometries. - Walking: use 0-500. Prefer 50-200 for short contours (minutes < 10 or meters < 5000), 300-500 as they grow. - Driving: use 1000-5000. Start at 2000, use 3000 if minutes > 10 or meters > 20000. Use 4000-5000 if near 60 minutes or 100000 meters.
coordinatesYesA coordinate object with longitude and latitude properties around which to center the isochrone lines. Longitude: -180 to 180, Latitude: -85.0511 to 85.0511
contours_colorsNoContour colors as hex strings without starting # (for example ff0000 for red. must match contours_minutes or contours_meters length if provided).
contours_metersNoDistances in meters. Distances must be in increasing order. Must be specified either contours_minutes or contours_meters.
contours_minutesNoContour times in minutes. Times must be in increasing order. Must be specified either contours_minutes or contours_meters.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
featuresYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds that output is in GeoJSON format suitable for map display, which is useful. No contradictions with 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 concise, with a clear introductory sentence and bullet-pointed use cases. It is front-loaded with the core functionality. However, there is a minor typo (extra quote at the end).

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?

The description covers common use cases and output format, but omits that the tool also supports distance-based contours (contours_meters) in addition to time-based ones. Given high schema coverage and existence of an output schema, the description is mostly complete but has this notable gap.

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 itself provides detailed parameter information. The description adds some context (e.g., return format) but does not significantly enhance understanding of individual parameters beyond what is in the schema.

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 that the tool computes reachable areas within a specified time and returns them as Polygons or LineStrings in GeoJSON. It provides common use cases that illustrate the tool's purpose. However, it does not explicitly differentiate this tool from siblings like buffer_tool or directions_tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes common use cases that imply when to use the tool (e.g., showing travel time areas, threshold checks). However, it lacks explicit guidance on when not to use it or how it compares to alternative tools such as distance_tool or buffer_tool.

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