Skip to main content
Glama
NeshanMaps

Neshan MCP Server

Official
by NeshanMaps

neshan_map_view

Generate an interactive map HTML file with markers, routes, and traffic overlay for local viewing.

Instructions

Generate an interactive Neshan map HTML file and save it locally.

Creates a fully interactive map page using the Neshan Maps SDK. Supports markers with popups and route polylines drawn on the map. The map auto-fits to show all markers and routes. Open the returned file_path in any browser to view the map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoomNoInitial zoom level (2–21). Auto-calculated when markers/routes are present.
titleNoPage title shown in the header bar.نقشه نشان
routesNoRoute objects to draw. Each needs either 'encoded_polyline' (the overview_polyline field returned by neshan_direction) or a raw 'coordinates' list.
map_keyNoNeshan Web SDK API key (different from service key). Without this the base map tiles won't load, but markers and routes are still drawn. Get one from platform.neshan.org.
markersNoMarker objects to place on the map.
show_poiNoShow points of interest labels on the map.
center_latNoFallback center latitude (used when no markers/routes given).
center_lngNoFallback center longitude.
show_trafficNoOverlay live traffic layer on the map.
Behavior4/5

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

With no annotations, the description discloses key behaviors: file creation, auto-fit behavior, behavior without map_key (markers/routes still work). It lacks details on file size, performance, or cleanup, but covers the main behavioral traits adequately.

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 (5 lines) and front-loaded with the main purpose. It could be slightly more structured with bullet points, but every sentence adds value and it avoids verbosity.

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

Completeness5/5

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

Given 9 parameters with thorough schema descriptions and no output schema, the description adequately explains the output (file_path to open in browser) and auto-fit behavior, making the tool's usage fully understandable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds context beyond the schema: explains auto-fit, file_path output, and map_key distinction from service key. This adds value, exceeding the baseline of 3.

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 states a specific verb ('Generate') and resource ('interactive Neshan map HTML file'), and clarifies it creates a page with markers and routes, distinguishing it from siblings like static maps or direction tools.

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 implies usage for interactive map creation but does not explicitly contrast with alternatives (e.g., static_map for images, deeplink for navigation), leaving the agent to infer when to choose this 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/NeshanMaps/Neshan-MCP'

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