Skip to main content
Glama
magiclane

Magic Lane MCP Server

Official
by magiclane
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Interactive Map

interactive_map

Display interactive maps with location markers, route visualization, isochrone reachability, round trip paths, and search result markers. Supports pan, zoom, and click interactions.

Instructions

Display an interactive map using MagicLane vector tiles and MapLibre GL JS directly in the conversation. Supports multiple display types: location view, route visualization with stops, isochrone reachability areas, round trip routes, and search result markers. The map supports pan, zoom, and click interactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
display_typeYesWhat to show on the interactive map. Exactly one of: "location": single point with optional label (default; use LocationDisplayParametersSchema). "routing": calculated route with origin/destination/stops (use RoutingParametersSchema). "isochrone": reachability polygon from a departure point (use IsochroneParametersSchema). "round_trip": circular loop from a departure point (use RoundTripParametersSchema). "search_results": POI/address search results as markers (use SearchParametersSchema).
zoomNoInitial map zoom level in [0, 16]. 0 = whole world, 8 = country, 12 = city (default), 14 = neighborhood, 16 = street. IGNORED when display_type is "routing", "isochrone", or "round_trip" - those auto-fit to data bounds.
parametersYesParameters for the chosen `display_type`. Shape MUST match `display_type`: "location": LocationDisplayParametersSchema; "routing": RoutingParametersSchema; "isochrone": IsochroneParametersSchema; "round_trip": RoundTripParametersSchema; "search_results": SearchParametersSchema.

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

Without annotations, the description carries full burden. It only mentions interactivity (pan, zoom, click) but does not disclose read-only nature, data requirements, or any side effects. This is insufficient for an agent to understand system impact.

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 extremely concise with only two sentences that front-load the main purpose and capabilities. Every word adds value, making it efficient for agent comprehension.

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 the high complexity (multiple display types, nested parameters) and no output schema, the description is insufficient. It does not explain return format, rendering behavior, or how results are presented to the user.

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 coverage is 100%, so the schema already provides detailed parameter descriptions. The tool description adds minimal extra meaning beyond listing display types. Baseline score of 3 is appropriate.

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 displays an interactive map using specific technologies (MagicLane, MapLibre GL JS) and lists supported display types. However, it does not differentiate from sibling tool static_map_render, which also renders maps, causing potential ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives like route_planner, isochrone_calculator, or static_map_render. The description lacks when-to-use or when-not-to-use instructions.

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