Skip to main content
Glama
magiclane

Magic Lane MCP Server

Official
by magiclane
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Isochrone Calculator

isochrone_calculator
Read-only

Calculate reachable areas within specified time or distance from a starting point, using driving, walking, cycling, or public transport.

Instructions

Generate isochrone polygons (areas reachable within a certain time or distance) from a given starting point. Accepts either coordinates or a place/address name. If an address is provided, this tool will internally convert it to coordinates. Useful for finding reachable areas for driving, walking, or cycling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transportNoTransport mode used to compute reachability. Exactly one of: "car" (default), "lorry"/"truck", "pedestrian", "bike", "public".car
typeNoCost model and units for the values in `ranges`. Exactly one of: "fastest" — `ranges` interpreted as SECONDS of travel time (default; valid for all transport modes). "shortest" — `ranges` interpreted as METERS of travel distance (valid for all transport modes). "economic" — energy-minimizing cost model; VALID ONLY for e-bikes (requires transport="bike" AND `vehicle.profile` set to a pedelec/spedelec sub-profile such as "city_pedelec"). Range units same as "fastest". Do NOT use for cars, trucks, regular bikes, or pedestrians. "scenic" — prefers scenic roads; valid for car, truck/lorry, and pedestrian. NOT valid for transport="bike". Range units same as "fastest".fastest
departureYesOrigin point from which reachability is computed. Provide "coordinates" (longitude, latitude) when known, or "location" to resolve from a place/address.
rangesYesOne or more range thresholds; each produces a separate isochrone polygon. UNITS depend on `type`: SECONDS when type="fastest"/"economic"/"scenic", METERS when type="shortest". Example: [600, 1800, 3600] with type="fastest": 10 min, 30 min, 60 min reachable areas. All values must be positive.
avoidNoRoad features to exclude. Array of zero or more of: "highway", "toll", "ferry", "unpaved", "turnaround", "traffic", "roadblocks". Empty array (default) means avoid nothing.
localeNoISO 639-2 / ISO 639-3 language code for any place names in the response. Default "en".en
vehicleNoVehicle profile used to apply road restrictions and energy modelling to the reachability calculation. REQUIRED for transport="truck"/"lorry" (dimensions/weight to avoid restricted roads). REQUIRED for electric vehicles (set `vehicle.fuel="electric"` and `vehicle.ev` for range-aware isochrones). REQUIRED for bike with type="economic" — set `vehicle.profile` to a pedelec/spedelec eBike variant. OPTIONAL for car/regular-bike/pedestrian — defaults apply when omitted.

Tool Definition Quality

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true (read-only) and openWorldHint=true (external data). The description adds value by noting that addresses are internally converted to coordinates, which is a behavioral detail not in annotations. No contradictions.

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 three sentences with no wasted words. It front-loads the core purpose, then explains input flexibility, and ends with a use-case statement. Every sentence earns its place.

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, nested objects, no output schema), the description is minimal. It does not explain output format (polygons) beyond the first sentence, nor provide usage tips for specific parameters like ranges or transport. However, the comprehensive schema descriptions partially compensate.

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% (all parameters have descriptions in the schema). The description mentions that the tool accepts coordinates or addresses, but this is already detailed in the schema. Thus, the description adds minimal additional meaning beyond the schema.

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 explicitly states that the tool generates isochrone polygons (areas reachable within a time or distance) from a starting point. It clearly distinguishes from siblings like route_planner (which provides point-to-point routes) by focusing on reachable areas.

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 mentions usefulness for driving, walking, or cycling, implying the tool is for reachability analysis. However, it does not explicitly state when to use this tool versus alternatives (e.g., route_planner for routes, geofence_manager for boundaries) or when not to use it. No exclusions or alternatives are provided.

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

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