MapNetwork MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_mapA | Generate a styled map centered on a single place. Example: generate_map(place="Tokyo Station") |
| generate_markers_mapB | Generate a map with multiple pinned locations. Example: generate_markers_map(markers=[{"label": "Tokyo Tower", "link": "https://www.tokyotower.co.jp/"}, {"label": "Zojoji Temple"}]) |
| generate_route_mapA | Compute a walking/driving route between two places and generate a map with it overlaid. Both endpoints are pinned on the map automatically — do not also call generate_markers_map for them. Example: generate_route_map(from="Tokyo Station", to="Tokyo Tower", mode="walking") |
| download_mapA | Check a pending generate_* job and download it once ready. If it's already done, returns the image immediately; otherwise waits internally (checking periodically) before returning — no need to wait between calls yourself. If still not ready when it returns, call it again with the same dataKey. Example: download_map(data_key="20260618aBcDeFgHiJ") |
| redownload_mapA | Re-download a prior map in a different color theme or format — instant, no regeneration. Example: redownload_map(data_key="20260618aBcDeFgHiJ", color_set="black") |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a clearly distinct operation: single-place maps, multi-marker maps, route maps, downloading a pending result, and re-downloading with different styling. The overlap between generate_map and generate_markers_map is minimal and the descriptions make the boundary clear.
All tool names follow a consistent verb_noun pattern using snake_case: generate_map, generate_markers_map, generate_route_map, download_map, redownload_map. The verb prefix clearly communicates the action while the noun identifies the target.
Five tools is well-scoped for a map generation server. Each tool covers a necessary part of the workflow—generating different map types, fetching results, and re-styling prior outputs—without redundancy or bloat.
The tool surface covers the full expected lifecycle: generate maps in three distinct forms, retrieve the async result, and re-download existing maps in alternate themes or formats. There are no obvious dead ends or missing core operations for the declared purpose.