Ultimaps MCP
Server Details
Turn your data into map images of countries, states, counties and ZIP codes with Ultimaps MCP server. Each map comes with a link to Ultimaps Studio, where you can keep editing it, export it, or publish an interactive version. No account needed: 30 maps per hour, PNG up to 1600px, with Ultimaps attribution.
- Status
- Healthy
- Uptime
- 100.0% over 38 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: list_maps discovers map ids, get_map_regions inspects one map's region keys, and render_map produces the image. The descriptions explicitly guide when to use each and explain that get_map_regions is rarely needed before rendering, reducing misselection.
All three tool names follow a consistent snake_case verb_noun pattern: list_maps, get_map_regions, render_map. The verbs are meaningful and the naming convention is uniform throughout.
Three tools are sufficient for this server's focused purpose: discovery, region inspection, and rendering. Each tool earns its place, and the surface is not bloated with redundant operations.
The tool surface covers the full workflow needed to render maps: finding maps, resolving region keys, and drawing the map with validation via dryRun. Extra capabilities such as pins, layers, legends, and output links are folded into render_map, leaving no obvious dead ends for the stated purpose.
Available Tools
3 toolsget_map_regionsGet map regionsARead-onlyIdempotentInspect
Look up one map: title, regionType, regionCount, labels, layers, and its regions as {key, title}, 200 per page.
You rarely need this before rendering. render_map accepts region names, codes and common aliases and auto-corrects typos, reporting what it matched.
Use it to build a dataset covering every region of a map, to see how a map names its regions, or to resolve a key render_map could not match.
query searches keys, titles and aliases, so no hits means the map really has no such region. Use offset for further pages.
| Name | Required | Description | Default |
|---|---|---|---|
| mapId | Yes | Map id from list_maps, e.g. "united-states", "europe", "united-states-california". | |
| query | No | Search region keys, titles and aliases, e.g. "saint" or "US-TX". Omit to page through every region. | |
| offset | No | Skip this many regions. Pages hold 200 regions; use the offset the previous result names. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a read-only, idempotent, non-destructive lookup. The description adds valuable behavior beyond annotations: it lists the returned fields, explains the 200-region pagination, and clarifies that a query miss means the map truly lacks that region.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the return shape and page size, then moves naturally into usage guidance and parameter behavior. Every sentence contributes distinct information without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only lookup with full schema coverage and no output schema, the description supplies enough return detail, pagination behavior, and usage guidance for correct invocation. No important behavioral or contextual gap remains.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds useful meaning beyond the schema by explaining that query searches keys, titles, and aliases and that no hits is a definitive absence, and by directing use of offset for further pages.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Look up one map' and returns its regions. It also names the returned fields and pagination size, making the tool's purpose distinct from list_maps and render_map.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says this is rarely needed before rendering and names render_map as the alternative that accepts names, codes, and aliases. It then gives concrete use cases: building a complete dataset, learning region naming, or resolving a key render_map could not match.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_mapsList mapsARead-onlyIdempotentInspect
List the maps Ultimaps can render: the world, continents, countries subdivided into states, provinces, counties or departments, and US ZIP code areas.
Each row is {id, title, regionType, layers, regionCount, labels}. id is the mapId for render_map and get_map_regions; it is the map's slug on ultimaps.com (the last path segment, not the whole URL) and always means the current edition.
regionCount is how many region keys a complete dataset needs. labels: false means the map has no region labels, so style.labels does nothing there. layers are the ids render_map's layers can turn on.
Pass query to search ids, titles, region types and categories (e.g. "counties", "germany", "africa").
Only call this when you don't know the id: common ids such as world, united-states and europe just work, and an unknown id usually comes back with the closest ids.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Search map ids, titles, region types and categories, e.g. "counties", "germany", "africa". Omit to list every map. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare a safe, read-only, idempotent operation, and the description adds substantial behavioral detail beyond them: the row shape, the meaning of `id` as a slug for the current edition, the meaning of `regionCount`, the effect of `labels: false` on `style.labels`, and how `layers` relate to `render_map`.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Although the description is multi-sentence, it is densely front-loaded and nearly every sentence conveys a distinct operational fact: return shape, id semantics, regionCount, labels, layers, query behavior, and usage constraint. There is very little waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description carries the burden of explaining return values, and it does so thoroughly via the row shape and field semantics. It also covers id reuse, query usage, and unknown-id behavior, making the definition complete for an agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the schema already documents that `query` searches ids, titles, region types, and categories with examples. The description largely repeats that same semantic content rather than adding syntax or constraints beyond what the schema provides, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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: 'List the maps Ultimaps can render,' then enumerates the map families. It also distinguishes its role from sibling tools by explaining that the returned `id` is the input for `render_map` and `get_map_regions`.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives explicit when-to-use guidance: 'Only call this when you don't know the id,' notes that common ids like `world` and `united-states` already work, and states the fallback behavior for unknown ids. That is unusually clear routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
render_mapRender mapAInspect
Draws a map of real places as an image: countries, states, counties or ZIP codes colored by data (a choropleth or heat map) or by category, with a legend, a title and pins. Borders come from real geographic data, not from an image model, and region names are matched for you. It draws only real places, never fictional or invented ones. The map is returned 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. Say what the numbers are withkind(andmidpointwhen they have a meaningful center,unitfor a short label unit): that is what gets percents, currencies, years and diverging scales right. When the data does not cover every region of the map, addnoData: trueso the legend explains the uncolored ones.categories: a label per region, e.g. {"values": {"France": "Euro", "Poland": "Złoty"}}. Colors are assigned automatically unless you setcolors.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. GetmapIdfrom list_maps if you don't know it. Also available: pins (locationswith lat/lon),title,legend(position,title,subtitle),style(theme, borders, region labels;style.labels.content: "value"prints each region's value instead of its name and"name_value"stacks the name above the value, both needingchoroplethorcategories;style.labels.fit(default "auto") shortens labels that don't fit or overlap and never hides one; any still overlapping are reported in alabels_overlapwarning with their keys), extralayers, andoutputsize. A data legend needs alegend.title: what is measured, its unit and the year ("Median household income (US$, 2023)"). An untitled legend leaves the reader guessing. Short units ("%", "°C", "t") go inchoropleth.unit, long ones ("litres per person") in the legend title.dryRun: truevalidates 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. SVG and PDF export are in Ultimaps Studio, from the edit link in the result. Every result includes an image link that works for 30 days, for chat apps that do not display images returned by tools. The result reports corrections, warnings, the resolved color plan, and an edit link that opens the map in Ultimaps Studio, where it can be edited, exported, or published as an interactive, clickable map to embed on a website (free account).
| Name | Required | Description | Default |
|---|---|---|---|
| mapId | Yes | Map 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. | |
| style | No | ||
| title | No | ||
| dryRun | No | Validate 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). | |
| layers | No | Extra 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. | |
| legend | No | ||
| output | No | Image 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. | |
| regions | No | Override 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 (in choropleth mode, a contrasting gray when the theme's region color is too close to the palette's lightest class). | |
| locations | No | Pin markers. They compose with every mode. | |
| categories | No | Categorical 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. | |
| choropleth | No | Numeric 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. Do send `kind` whenever you know what the numbers are, `midpoint` when they have a meaningful center, and a short `unit`: the values alone cannot tell 42% from 0.42 or a change from a level. | |
| onUnmatched | No | warn = 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. Region keys in `style.labels.hide` count too: a typo there is a 400 under error. | warn |
Output Schema
| Name | Required | Description |
|---|---|---|
| dryRun | Yes | |
| format | No | Image format; absent on dry runs. |
| legend | No | Dry runs: legend preview, [{label, color}] or {points, stops} for a gradient. |
| editUrl | No | Opens this map in Ultimaps Studio to edit, export, or publish it as an interactive map that can be embedded on a website. |
| artifact | No | A stored copy of the image at a public, unguessable link that expires. Set on every render while link storage is available. |
| embedUrl | No | Keyless GET image URL, when the render is shareable that way. |
| renderId | Yes | The API render id; quote it to Ultimaps support. |
| warnings | Yes | |
| choropleth | No | The resolved choropleth plan. Dry runs add `reason` and `breaks`. |
| regionMatching | Yes | |
| keylessRemaining | No | Anonymous renders left this hour: for this conversation, or for this AI service when it sends no conversation id. |
| matchingTruncated | Yes | True when `corrected`/`unmatched` list only the first 5 of their counts. Repeat the call with dryRun: true for the full report. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true) already flag this as a non-idempotent, non-destructive, open-world content-generation operation. The description goes well beyond them, disclosing rate limits (30/hour, 5/minute without key), 1600px anonymous caps, Ultimaps attribution, the 30-day image link, and what the result reports (corrections, warnings, edit link). None of this contradicts annotations; readOnlyHint=false is consistent with an operation that renders and writes results. The extra context is meaningful but the safety profile is already covered, so a 3 is appropriate rather than a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is front-loaded with the core purpose and organized into bullets, with each mode introduced before details. It's long, and parts (choropleth/categories mode explanation, label-content behavior) repeat what the schema already says, but the length is largely justified by the tool's complexity. Efficient enough, with some schema redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 12-parameter tool with nested objects and an output schema, the description covers what an agent needs: purpose, mode selection, matching behavior, limits, and what the result reports. Return-value explanation is handled by the output schema, and the description fills the remaining gaps correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 75%, so the schema already does a lot of work. The description adds real value beyond it: it explains region key matching (names, ISO/FIPS codes, aliases, auto-correction), that choropleth and categories are mutually exclusive, the kind/midpoint/unit semantics with '42%' vs '0.42' guidance, that noData explains uncolored regions, and that a data legend requires a title. This compensation for the remaining coverage gap is substantive.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Opens with a specific verb+resource: 'Draws a map of real places as an image: countries, states, counties or ZIP codes colored by data...' It explicitly names and defers to both siblings ('no need to call get_map_regions first', 'Get mapId from list_maps'), so an agent can distinguish it immediately.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
States the choropleth vs categories modes are mutually exclusive, when regions acts as an override layer, when to send noData for incomplete coverage, when to send kind/midpoint/unit, and when to use dryRun. Alternatives and the conditions that select them are spelled out rather than left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
render_map2 fields changed- changed
Output schema / properties / editUrl / descriptionPrevious value: -"Opens this map in Ultimaps Studio for editing or export."New value: +"Opens this map in Ultimaps Studio to edit, export, or publish it as an interactive map that can be embedded on a website." - added
Output schema / properties / warnings / items / properties / noticeAdded value: +{ + "description": "Plain-language sentence the map viewer shows the user, when the warning has one.", + "type": "string" +}
1 tool update
- Changed
render_map1 field changed- changed
Input schema / properties / output / properties / format / descriptionPrevious value: -"`png` (default) or `svg`. SVG needs a Pro API key and is returned as a link. PDF is not available."New value: +"`png` (default) or `svg`. `svg` works only with an API key that allows it, and is returned as a link; otherwise export SVG in Ultimaps Studio. PDF is not available."
1 tool update
- Changed
render_map7 fields changed- changed
Input schema / properties / choropleth / properties / noData / descriptionPrevious value: -"Adds a \"No data\" row to the legend for regions without a value: true, or {\"label\": \"Not reported\"}. Off unless you send it. Send it whenever your data does not cover the whole map (the result reports how many regions have no value); without it those regions are drawn in a grey the legend does not explain. With full coverage the row is left out. A `nodata_low_contrast` warning means the default fill for those regions is hard to tell from the palette (grey palettes): send `noDataColor`."New value: +"Adds a \"No data\" row to the legend for regions without a value: true, or {\"label\": \"Not reported\"}. Off unless you send it. Send it whenever your data does not cover the whole map (the result reports how many regions have no value); without it those regions are drawn in a gray the legend does not explain. With full coverage the row is left out. A `nodata_low_contrast` warning means the default fill for those regions is hard to tell from the palette (gray palettes): send `noDataColor`." - changed
Input schema / properties / choropleth / properties / noDataColor / descriptionPrevious value: -"Fill for regions absent from `values`. Choropleth mode only. Overrides `style.defaultRegionColor` when both are set. When neither is set, the theme's region color is used if it stays apart from the palette (CIEDE2000 ≥ 12 from the lightest class, ≥ 8 from every class) or is transparent by design; otherwise a light, slightly theme-tinted grey that does and keeps the region borders visible, so missing data never reads as the lowest class or as the neutral of a diverging palette. Grey palettes can leave no such color: the theme color is then darkened and a `nodata_low_contrast` warning asks for an explicit `noDataColor`.\n"New value: +"Fill for regions absent from `values`. Choropleth mode only. Overrides `style.defaultRegionColor` when both are set. When neither is set, the theme's region color is used if it stays apart from the palette (CIEDE2000 ≥ 12 from the lightest class, ≥ 8 from every class) or is transparent by design; otherwise a light, slightly theme-tinted gray that does and keeps the region borders visible, so missing data never reads as the lowest class or as the neutral of a diverging palette. Gray palettes can leave no such color: the theme color is then darkened and a `nodata_low_contrast` warning asks for an explicit `noDataColor`.\n" - changed
Input schema / properties / layers / properties / admin0 / descriptionPrevious value: -"Surrounding land, as a filled area of neighbouring countries or states."New value: +"Surrounding land, as a filled area of neighboring countries or states." - changed
Input schema / properties / layers / properties / cities / descriptionPrevious value: -"Major cities as labelled points."New value: +"Major cities as labeled points." - changed
Input schema / properties / legend / properties / position / descriptionPrevious value: -"left/right take a column carved from the map area (180 px, at most 30% of the width); top/bottom take a horizontal band between the title and the map. Absent = picked per render: inside the map over empty space (sea, the margin beside a narrow map) when the legend fits there clear of land, else gradient/steps go to the bottom band and item/group legends to the left column or the bottom band, whichever leaves the map larger. Leave it out unless you need the legend outside the map. Gradient and steps legends are horizontal-only, so left/right becomes bottom with a warning. Band items wrap into rows; a bar too wide for a narrow image is reported as a `legend_overflow` warning."New value: +"left/right take a column carved from the map area (180 px, widened up to 260 px for long labels or a legend title, at most 30% of the width); top/bottom take a horizontal band between the title and the map. Absent = picked per render: inside the map over empty space (sea, the margin beside a narrow map) when the legend fits there clear of land, else gradient/steps go to the bottom band and item/group legends to the left column or the bottom band, whichever leaves the map larger. Leave it out unless you need the legend outside the map. Gradient and steps legends are horizontal-only, so left/right becomes bottom with a warning. Band items wrap into rows; a bar too wide for a narrow image is reported as a `legend_overflow` warning." - changed
Input schema / properties / regions / descriptionPrevious value: -"Override 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 (in choropleth mode, a contrasting grey when the theme's region color is too close to the palette's lightest class).\n"New value: +"Override 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 (in choropleth mode, a contrasting gray when the theme's region color is too close to the palette's lightest class).\n" - changed
Input schema / properties / style / properties / labels / properties / fit / descriptionPrevious value: -"`auto` shortens labels that don't fit or overlap and never hides one; `off` draws every label in full. Under `auto` a `name_value` label too big for its region, or overlapping a higher-priority one, drops to its value (choropleth; the legend only gives a range) or its name (categories; the fill already says the category). Priority: curated outside labels (small regions labelled beside the map), then larger regions. Labels still overlapping are drawn and reported in a `labels_overlap` warning. Studio's own default is off; a map opened in Studio from a render keeps the value sent."New value: +"`auto` shortens labels that don't fit or overlap and never hides one; `off` draws every label in full. Under `auto` a `name_value` label too big for its region, or overlapping a higher-priority one, drops to its value (choropleth; the legend only gives a range) or its name (categories; the fill already says the category). Priority: curated outside labels (small regions labeled beside the map), then larger regions. Labels still overlapping are drawn and reported in a `labels_overlap` warning. Studio's own default is off; a map opened in Studio from a render keeps the value sent."
1 tool update
- Changed
render_map26 fields changed- changed
Input schema / properties / choropleth / descriptionPrevious value: -"Numeric 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."New value: +"Numeric 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. Do send `kind` whenever you know what the numbers are, `midpoint` when they have a meaningful center, and a short `unit`: the values alone cannot tell 42% from 0.42 or a change from a level." - changed
Input schema / properties / choropleth / properties / format / descriptionPrevious value: -"Number format for every choropleth surface: class labels, gradient ticks and value labels. Always pass an object, e.g. {\"preset\": \"compact\"}, never a bare string. Presets: `auto` (default, inferred from magnitude), `plain` (39,538,223), `compact` (39.5M), `percent` (the input is a FRACTION, so 0.42 prints as 42% and 0.423 as 42.3%, because the preset trims trailing zeros. An explicit {\"style\": \"percent\", \"decimals\": 1} keeps them and prints 42.0%. For data already in percent points use {\"suffix\": \"%\"}), `currency` ($39,538,223). Or combine options, e.g. {\"decimals\": 1, \"suffix\": \"M\"} or {\"style\": \"currency\", \"currency\": \"EUR\"}. {\"d3\": \"~s\"} is a raw d3-format escape hatch. The result echoes the resolved format."New value: +"Number format for every choropleth surface: class labels, gradient ticks and value labels. Always pass an object, e.g. {\"preset\": \"compact\"}, never a bare string. Presets: `auto` (default, inferred from magnitude), `plain` (39,538,223), `compact` (39.5M), `percent` (the input is a FRACTION, so 0.42 prints as 42% and 0.423 as 42.3%, because the preset trims trailing zeros. An explicit {\"style\": \"percent\", \"decimals\": 1} keeps them and prints 42.0%. For data already in percent points use {\"suffix\": \"%\"}), `currency` ($39,538,223). Or combine options, e.g. {\"decimals\": 1, \"suffix\": \"M\"} or {\"style\": \"currency\", \"currency\": \"EUR\"}. {\"d3\": \"~s\"} is a raw d3-format escape hatch. Add \"locale\" for a non-US number style: \"de-DE\" (1.234,5 / 1,2 Mio.), \"fr-FR\" (1 234,5), \"es-ES\", \"it-IT\", \"pt-BR\", \"de-CH\" (1’234.5), \"en-IN\" (12,34,567 / 12L), \"nl-NL\", \"pl-PL\", \"sv-SE\"; it combines with presets and d3, and {\"locale\": \"de-DE\"} alone is the automatic format in that style. The result echoes the resolved format." - added
Input schema / properties / choropleth / properties / format / properties / localeAdded value: +{ + "default": "en-US", + "description": "Number style: separators, currency placement and compact suffixes. `{\"decimals\": 1, \"locale\": \"de-DE\"}` turns 1234567.5 into \"1.234.567,5\"; with `compact: true` it gives \"1,2 Mio.\". Combines with `preset` and `d3`; on its own (`{\"locale\": \"de-DE\"}`) it is the automatic format in that number style.\n", + "enum": [ + "en-US", + "de-DE", + "fr-FR", + "es-ES", + "it-IT", + "pt-BR", + "de-CH", + "en-IN", + "nl-NL", + "pl-PL", + "sv-SE" + ], + "type": "string" +} - added
Input schema / properties / choropleth / properties / kindAdded value: +{ + "description": "What the numbers are. Send it whenever you know. `percent` = already ×100 (42 prints \"42%\"), `fraction` = a 0–1 share (0.42 prints \"42%\"), `currency` (set `unit` to the code, e.g. \"EUR\"), `year` (1788, no separator), `change` (signed labels, diverging around 0), or `count`, `rate`, `index`. Once a kind is given, the palette is diverging only with `midpoint` or `kind: \"change\"`, so data that merely dips below zero stays sequential.", + "enum": [ + "count", + "rate", + "percent", + "fraction", + "currency", + "change", + "year", + "index" + ], + "type": "string" +} - added
Input schema / properties / choropleth / properties / legendEndLabelsAdded value: +{ + "description": "Steps legends: also print the two outer ends of the bar (ignored for groups and gradient legends). An end that the automatic breaks left open, or that the data reaches past, reads \"< 10\" / \"≥ 90\" rather than a round bound the data never reaches. Groups legends already print every range and gradients their ends, so only steps change. Default false.\n", + "type": "boolean" +} - changed
Input schema / properties / choropleth / properties / method / descriptionPrevious value: -"Break method. Absent = suggested from the data. quantile = equal number of regions per class, equalInterval = equal-width value intervals, jenks = natural breaks (minimal within-class variance), pretty = rounded human-readable edges. Additive-only enum: more methods may be added, none removed.\n"New value: +"Break method. Absent = round, publishable edges picked from the data (a constant step such as 0 · 10 · 20 · 30, or a 1-2-5 ladder such as 0 · 10K · 25K · 50K · 100K for skewed data), reported as `pretty`. quantile = equal number of regions per class, equalInterval = equal-width value intervals, jenks = natural breaks (minimal within-class variance), pretty = rounded human-readable edges. Additive-only enum: more methods may be added, none removed.\n" - added
Input schema / properties / choropleth / properties / midpointAdded value: +{ + "description": "The meaningful center of the data: 0 for a change or balance, 100 for an index where 100 is the reference (EU27 = 100), 1 for a ratio. Gives a diverging palette with its neutral color on this value. Leave it out for one-directional data.", + "type": "number" +} - added
Input schema / properties / choropleth / properties / noDataAdded value: +{ + "additionalProperties": false, + "description": "Adds a \"No data\" row to the legend for regions without a value: true, or {\"label\": \"Not reported\"}. Off unless you send it. Send it whenever your data does not cover the whole map (the result reports how many regions have no value); without it those regions are drawn in a grey the legend does not explain. With full coverage the row is left out. A `nodata_low_contrast` warning means the default fill for those regions is hard to tell from the palette (grey palettes): send `noDataColor`.", + "properties": { + "label": { + "maxLength": 40, + "minLength": 1, + "type": "string" + } + }, + "type": [ + "boolean", + "object" + ] +} - changed
Input schema / properties / choropleth / properties / noDataColor / descriptionPrevious value: -"Fill for regions absent from `values`. Choropleth mode only. Overrides `style.defaultRegionColor` when both are set.\n"New value: +"Fill for regions absent from `values`. Choropleth mode only. Overrides `style.defaultRegionColor` when both are set. When neither is set, the theme's region color is used if it stays apart from the palette (CIEDE2000 ≥ 12 from the lightest class, ≥ 8 from every class) or is transparent by design; otherwise a light, slightly theme-tinted grey that does and keeps the region borders visible, so missing data never reads as the lowest class or as the neutral of a diverging palette. Grey palettes can leave no such color: the theme color is then darkened and a `nodata_low_contrast` warning asks for an explicit `noDataColor`.\n" - changed
Input schema / properties / choropleth / properties / palette / descriptionPrevious value: -"ColorBrewer palette id (the server matches case-insensitively). Absent = suggested from the data: diverging when the values cross zero (rdbu when they sit symmetrically around zero, rdylgn when they do not), sequential blues otherwise. Note that `rdylgn` only comes back out. It is not in the enum above, and requesting it is a `400`. Sequential palettes suit one-directional data, and diverging palettes (rdbu, brbg, spectral, piyg, prgn, puor, rdgy, rdylbu) suit data around a midpoint.\n"New value: +"ColorBrewer palette id (the server matches case-insensitively). Absent = suggested: `rdbu` centered on `midpoint` when one is given (or `kind` is `change`); with no hints, `rdbu` centered on 0 when the values spread on both sides of zero; sequential blues otherwise. Sequential palettes suit one-directional data, and diverging palettes (rdbu, brbg, spectral, piyg, prgn, puor, rdgy, rdylbu) suit data around a midpoint.\n" - added
Input schema / properties / choropleth / properties / unitAdded value: +{ + "description": "Short unit printed on every label, up to 16 characters: \"%\", \"°C\", \"t\", \"km²\". Put long units (\"litres of pure alcohol per person\") in `legend.title` instead. With `kind: \"currency\"` it is the currency code or symbol. Ignored for `kind: \"fraction\"` and when `format` is set, except {\"locale\": \"de-DE\"} (or {\"preset\": \"auto\", \"locale\": \"de-DE\"}), which keeps kind and unit in that number style. An explicit `format` decides only the labels: `kind` and `midpoint` still decide sequential vs diverging.", + "maxLength": 16, + "minLength": 1, + "type": "string" +} - changed
Input schema / properties / legend / properties / position / descriptionPrevious value: -"left/right take a column carved from the map area (180 px, at most 30% of the width); top/bottom take a horizontal band between the title and the map. Absent = left for item/group legends, bottom for gradient/steps. Gradient and steps legends are horizontal-only, so left/right becomes bottom with a warning. Legends do not wrap: a wide legend on a narrow image can overflow, reported as a `legend_overflow` warning."New value: +"left/right take a column carved from the map area (180 px, at most 30% of the width); top/bottom take a horizontal band between the title and the map. Absent = picked per render: inside the map over empty space (sea, the margin beside a narrow map) when the legend fits there clear of land, else gradient/steps go to the bottom band and item/group legends to the left column or the bottom band, whichever leaves the map larger. Leave it out unless you need the legend outside the map. Gradient and steps legends are horizontal-only, so left/right becomes bottom with a warning. Band items wrap into rows; a bar too wide for a narrow image is reported as a `legend_overflow` warning." - added
Input schema / properties / legend / properties / subtitleAdded value: +{ + "description": "Line under the legend title, at the label size in the regular weight, e.g. the source or the base year. Same wrapping as `title`.\n", + "maxLength": 160, + "minLength": 1, + "type": "string" +} - added
Input schema / properties / legend / properties / titleAdded value: +{ + "description": "Heading above the legend rows. Send one for every data legend: what is measured, its unit and the year, e.g. \"Median household income (US$, 2023)\". It is never derived from `choropleth.unit`: short units (\"%\", \"°C\") go in `unit` and print on every label, long ones belong here. Long titles wrap to fit the legend; `\\n` forces a break.", + "maxLength": 120, + "minLength": 1, + "type": "string" +} - changed
Input schema / properties / onUnmatched / descriptionPrevious value: -"warn = 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.\n"New value: +"warn = 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. Region keys in `style.labels.hide` count too: a typo there is a 400 under error.\n" - changed
Input schema / properties / output / properties / height / descriptionPrevious value: -"Optional. When omitted, derives as a snug fit: the map's aspect ratio applied to the map area that remains after the title band (50 px) and any left/right legend column take their cut. A top/bottom legend adds its band (60 px for item legends, 70 px for gradient/steps bars) on top of that. An explicit height is delivered exactly, and the title and legend then shrink the map rather than the canvas.\n"New value: +"Optional. When omitted, derives as a snug fit: the map's aspect ratio applied to the map area that remains after the title band (50 px) and any left/right legend column take their cut. A top/bottom legend adds its band (60 px for item legends, 70 px for gradient/steps bars, plus the height of a `legend.title`/`subtitle`) on top of that. A left/right legend too tall for that canvas (many items, a wrapped title) grows the derived height until it fits. An explicit height is delivered exactly, and the title and legend then shrink the map rather than the canvas.\n" - changed
Input schema / properties / regions / descriptionPrevious value: -"Override 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.\n"New value: +"Override 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 (in choropleth mode, a contrasting grey when the theme's region color is too close to the palette's lightest class).\n" - changed
Input schema / properties / style / properties / labels / descriptionPrevious value: -"Region labels, off by default. Each map ships its own curated label set; on a map with `labels: false` in list_maps, `show: true` renders nothing and a `labels_unavailable` warning is reported."New value: +"Region labels, off by default. Each map ships its own curated label set; on a map with `labels: false` in list_maps, `show: true` renders nothing and a `labels_unavailable` warning is reported. `content`: \"name\" (default), \"value\" (the choropleth number in the legend's format, or the category label; regions without data get no label) or \"name_value\" (name above value; regions without data show the name only). `fit`: \"auto\" (default) shortens labels that don't fit or overlap (to the value on a choropleth, the name on a category map); labels never disappear, and any still overlapping are listed in a `labels_overlap` warning. \"off\" draws every label in full. `hide`: region keys whose label never shows (matched like data keys). A typo is auto-corrected or reported as unmatched; under `onUnmatched: \"error\"` an unmatched key fails the request like a data key." - changed
Input schema / properties / style / properties / labels / properties / content / descriptionPrevious value: -"What each label prints. `name` is the region's name. `value` prints the region's choropleth number instead, formatted by the resolved `choropleth.format` (the same string the legend and tooltips show). Regions without a value get no label. Requires `choropleth`. With `categories`, or with neither, it is a `validation_error`. Labels are not collision-checked: a long number in a small region overflows it, exactly as in Studio."New value: +"What each label prints. `name` is the region's name. `value` prints the region's value instead: the choropleth number formatted by the resolved `choropleth.format` (the same string the legend and tooltips show), or the category label. Regions without a value get no label. `name_value` prints the name with the value on a line below it; regions without a value show the name only. Both value modes require `choropleth` or `categories`; with neither it is a `validation_error`." - changed
Input schema / properties / style / properties / labels / properties / content / enumPrevious value: -[ - "name", - "value" -]New value: +[ + "name", + "value", + "name_value" +] - added
Input schema / properties / style / properties / labels / properties / fitAdded value: +{ + "default": "auto", + "description": "`auto` shortens labels that don't fit or overlap and never hides one; `off` draws every label in full. Under `auto` a `name_value` label too big for its region, or overlapping a higher-priority one, drops to its value (choropleth; the legend only gives a range) or its name (categories; the fill already says the category). Priority: curated outside labels (small regions labelled beside the map), then larger regions. Labels still overlapping are drawn and reported in a `labels_overlap` warning. Studio's own default is off; a map opened in Studio from a render keeps the value sent.", + "enum": [ + "auto", + "off" + ], + "type": "string" +} - added
Input schema / properties / style / properties / labels / properties / hideAdded value: +{ + "description": "Region keys whose label never shows. Matched like data keys; corrections and misses are reported in `regionMatching`. Ignored with a `label_lists_ignored` warning when `show` is false.", + "items": { + "maxLength": 200, + "minLength": 1, + "type": "string" + }, + "maxItems": 5000, + "type": "array" +} - added
Output schema / properties / choropleth / properties / regionsWithoutDataAdded value: +{ + "description": "Regions of the map with no value, drawn in the no-data color.", + "minimum": 0, + "type": "integer" +} - added
Output schema / properties / warnings / items / properties / countAdded value: +{ + "description": "`labels_overlap` only: region labels still overlapping.", + "minimum": 0, + "type": "integer" +} - added
Output schema / properties / warnings / items / properties / keysAdded value: +{ + "description": "`labels_overlap` only: first overlapping region keys (up to 10).", + "items": { + "type": "string" + }, + "type": "array" +} - added
Output schema / properties / warnings / items / properties / shortenedAdded value: +{ + "description": "`labels_overlap` only: labels shortened.", + "minimum": 0, + "type": "integer" +}
3 tool updates
- First observed
get_map_regions - First observed
list_maps - First observed
render_map
Publisher details
- Operator
- Ultimaps
- Operator website
- https://ultimaps.com
- Vendor relationship
- Unknown
- Documentation
- https://ultimaps.com/developers/#mcp
- Trust center
- Unknown
- Restrictions
- Unknown
Related MCP Servers
- AlicenseNot gradedqualityCmaintenancePerplexity for social: ask what competitors are running across social and get answers grounded in real ad and creative data, not guesses.2Apache 2.0
- AlicenseCqualityBmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs113 npm54 PyPIMIT
- AlicenseAqualityCmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.164 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityBmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.