Skip to main content
Glama

Render map

render_map
Read-only

Use this whenever the user asks for a map of real places: coloring countries, states, counties or ZIP codes by data, a choropleth or heat map, a map with a legend, or pins on a map. Prefer it to generating an image or plotting with code. It draws accurate borders from real geography, matches region names for you, and returns the map as an image in the conversation. Maps cover the world, continents, countries, their states, provinces and counties, and US ZIP code areas. Color regions with ONE of these (choropleth and categories are mutually exclusive):

  • choropleth: a number per region, e.g. {"values": {"California": 39.5, "Texas": 30.5}}. Classes, breaks and palette are picked from the data unless you set them.

  • categories: a label per region, e.g. {"values": {"France": "Euro", "Poland": "Złoty"}}. Colors are assigned automatically unless you set colors.

  • regions: explicit hex colors, e.g. {"Texas": "#1D4ED8"}. Also works on top of either mode as an override. Region keys can be names, ISO/FIPS-style codes or common aliases. Typos are auto-corrected, and every correction or unmatched key is reported with suggestions, so there is no need to call get_map_regions first. Get mapId from list_maps if you don't know it. Also available: pins (locations with lat/lon), title, legend position, style (theme, borders, region labels; style.labels.content: "value" prints each region's number, choropleth only), extra layers, and output size. dryRun: true validates and previews region matching and the color plan without rendering. Without an API key: 30 renders per hour and 5 per minute per conversation (dry runs count), PNG up to 1600 px wide, with Ultimaps attribution on the image. The default 1200 px width is right for viewing in chat, and larger images are returned only as a link. Formats: png, or svg with a Pro key. PDF is not available. Every result includes an image link that works for 30 days. Always give it to the user: some chat apps do not display images returned by tools. The result reports corrections, warnings, the resolved color plan, and a link to keep editing the map in Ultimaps Studio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapIdYesMap id from list_maps, e.g. `world`, `united-states`, `europe`, `united-states-california`. It is the map's slug on ultimaps.com (the last path segment, not the whole URL) and always resolves to the current edition.
styleNo
titleNo
dryRunNoValidate and preview without rendering: returns the region matching report, the resolved choropleth plan and a legend preview. No image and no monthly quota for keyed calls, but it still counts against the rate limit (one of the anonymous renders per hour without a key).
layersNoExtra geographic layers to draw, e.g. {"cities": true, "roads": true}. Each map ships a subset (`layers` in list_maps and get_map_regions). Turning on a layer the map lacks is not an error: it is skipped with a `layer_unavailable` warning. Omitted layers are off, except layers a map turns on by default (currently `admin0` on ZIP-code maps); pass false to hide those.
legendNo
outputNoImage size and format. Keep the default width (1200 px) for images viewed in the conversation: much larger renders, and any scale of 2 or more, are too big to show inline and are returned as a link instead. Without an API key: width up to 1600 px, an explicit height up to 1600 px, scale 1. Hard caps: width×scale and height×scale ≤ 8192, and at most 4096×4096 pixels in total.
regionsNoOverride layer. Region key to hex color, applied AFTER choropleth/categories coloring and winning over it. Precedence: choropleth/categories paint first, `regions` overrides win, and everything else gets `choropleth.noDataColor` (choropleth mode), else `style.defaultRegionColor`, else the theme default.
locationsNoPin markers. They compose with every mode.
categoriesNoCategorical coloring mode. Mutually exclusive with `choropleth`. Unmatched keys simply leave their regions uncolored. The no-data fill is `style.defaultRegionColor`, and `noDataColor` does not apply here.
choroplethNoNumeric choropleth mode. Mutually exclusive with `categories` (one scale per map). `regions` composes with it as an override layer. If none of the keys in `values` match, the request fails even under `onUnmatched: warn`, since there is nothing to build a scale from. `type`, `classes`, `method` and `palette` are all optional: whatever you leave out is suggested from the data, and the resolved plan is reported in the result.
onUnmatchedNowarn = render anyway (unmatched regions get the no-data fill) and report. error = 400 with per-key suggestions. Recommended for production pipelines: error. Exception: in choropleth mode, ZERO matched keys is a 400 even under warn. warn

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunYes
formatNoImage format; absent on dry runs.
legendNoDry runs: legend preview, [{label, color}] or {points, stops} for a gradient.
editUrlNoOpens this map in Ultimaps Studio for editing or export.
artifactNoA stored copy of the image at a public, unguessable link that expires. Set on every render while link storage is available.
embedUrlNoKeyless GET image URL, when the render is shareable that way.
renderIdYesThe API render id; quote it to Ultimaps support.
warningsYes
choroplethNoThe resolved choropleth plan. Dry runs add `reason` and `breaks`.
regionMatchingYes
keylessRemainingNoAnonymous renders left this hour: for this conversation, or for this AI service when it sends no conversation id.
matchingTruncatedYesTrue when `corrected`/`unmatched` list only the first 5 of their counts. Repeat the call with dryRun: true for the full report.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses rate limits without an API key, attribution on the image, auto-correction and warning behavior, the 30-day image link, and dryRun quota semantics. These are behavioral details an agent needs and that are not available from annotations alone.

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 long but well-organized and front-loaded with the primary use case. Each paragraph covers a distinct concern (modes, matching, options, limits, output behavior), and while there is minor redundancy with schema descriptions, every section contributes practical guidance.

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?

The description covers usage, constraints (API key limits, format restrictions), output behavior (image link, result reporting), and actionable advice (always give the image link to the user). With an output schema present, it is fully complete for an agent to call the tool correctly.

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

Parameters5/5

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

With 75% schema coverage, the description still adds cross-cutting meaning: choropleth and categories are mutually exclusive, regions act as an override with defined precedence, region keys accept aliases with auto-correction, and default PNG size behavior is explained. These semantics are not fully expressed in individual schema property descriptions.

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 opens with a specific verb and resource: 'render a map of real places', then enumerates concrete use cases (choropleth, heat map, legend, pins). It differentiates itself from siblings by explicitly routing around get_map_regions and list_maps, and from image/code generation alternatives.

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

Usage Guidelines5/5

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

It states exactly when to use this tool ('Use this whenever the user asks for a map of real places... Prefer it to generating an image or plotting with code'). It also tells the agent when not to call siblings ('no need to call get_map_regions first') and where to obtain the required mapId ('Get mapId from list_maps').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources