Skip to main content
Glama

Revise a map you bought (free)

revise_map

Re-export a map bought with make_map, free for 7 days: change labels, annotations, styling, overlays or page elements. The frame must stay the same -- address or center, groundWidthM, pageSize, orientation, dpi. Requires the mapId make_map returned.

Input Schema

NameRequiredDescriptionDefault
dpiNo
mapIdNoRevise a map you already bought. Returned as X-Map-Id on your paid export. Re-exports are free for 7 days as long as the FRAME is unchanged — change labels, styling, overlays and page elements freely; changing address, center, groundWidthM, pageSize, orientation or dpi makes it a different map.
titleNoTitle block heading. Defaults to the address.
centerNo[longitude, latitude] in WGS84. Alternative to address.
formatNopdf
addressNoUS street address, city and state. Geocoded via the US Census.
overlaysNoThematic layers drawn under the annotations. A legend is added automatically. fema-flood: regulated floodplain (blank means no mapped hazard — FEMA draws Zone X with no symbol). nwi-wetlands: USFWS National Wetlands Inventory.
pageSizeNotabloid
autoLabelNoDraft tenant callouts from OpenStreetMap and road names from Census TIGER before drawing your own. Use this when you do not know what is at the location. Pass an object to control how many: fewer labels is the simplest cure for a crowded page.
labelScaleNoText size multiplier applied to every annotation that does not set its own textScale. Drop to ~0.8 to fit more labels; raise for a map read at arm’s length.
annotationsNoCallouts to draw. Placement, collision avoidance and leader lines are automatic.
orientationNoportrait
groundWidthMNoTrue ground width of the frame in meters. 500 fits a typical retail plaza; 20000-40000 makes a regional map, where autoLabel drafts cities, highway shields and water instead of tenants.
pageElementsNoPage furniture. Turn elements off to free up room for labels.
imagerySourceIdNoImagery source id. Defaults to the sharpest source covering the frame.
titleBlockScaleNoSize multiplier for the title block.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / annotations / items / properties / boxColor / maxLength
      Previous value: -32New value: +40
    • addedInput schema / properties / annotations / items / properties / boxColor / pattern
      Added value: +"^(#[0-9a-f]{3,8}|[a-z]{3,20}|rgba?\\(\\s*[\\d.]+%?\\s*(,\\s*[\\d.]+%?\\s*){2,3}\\))$"
    • changedInput schema / properties / annotations / items / properties / color / maxLength
      Previous value: -32New value: +40
    • addedInput schema / properties / annotations / items / properties / color / pattern
      Added value: +"^(#[0-9a-f]{3,8}|[a-z]{3,20}|rgba?\\(\\s*[\\d.]+%?\\s*(,\\s*[\\d.]+%?\\s*){2,3}\\))$"
    • changedInput schema / properties / annotations / items / properties / inkColor / maxLength
      Previous value: -32New value: +40
    • addedInput schema / properties / annotations / items / properties / inkColor / pattern
      Added value: +"^(#[0-9a-f]{3,8}|[a-z]{3,20}|rgba?\\(\\s*[\\d.]+%?\\s*(,\\s*[\\d.]+%?\\s*){2,3}\\))$"
    • changedInput schema / properties / annotations / items / properties / markColor / maxLength
      Previous value: -32New value: +40
    • addedInput schema / properties / annotations / items / properties / markColor / pattern
      Added value: +"^(#[0-9a-f]{3,8}|[a-z]{3,20}|rgba?\\(\\s*[\\d.]+%?\\s*(,\\s*[\\d.]+%?\\s*){2,3}\\))$"
    • changedInput schema / properties / annotations / items / properties / outlineColor / maxLength
      Previous value: -32New value: +40
    • addedInput schema / properties / annotations / items / properties / outlineColor / pattern
      Added value: +"^(#[0-9a-f]{3,8}|[a-z]{3,20}|rgba?\\(\\s*[\\d.]+%?\\s*(,\\s*[\\d.]+%?\\s*){2,3}\\))$"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already mark this as a non-read-only, open-world operation. The description adds useful behavioral context: the 7-day free re-export window, the requirement for a make_map-returned mapId, and the crucial rule that frame parameters are immutable while labels, annotations, styling, overlays, and page elements can change.

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 front-loaded with the core action and free-window condition, then immediately gives the frame constraint and mapId requirement. Every sentence earns its place, with no repetition of schema details.

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

Completeness4/5

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

For a 16-parameter nested tool, the description supplies the key behavioral and invocation constraints, and the rich schema covers most parameter details. It does not mention previewing or checking a map first, but that is a minor gap given the available schema and annotations.

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 75%, so the schema already documents most parameters. The description adds cross-parameter meaning by grouping address, center, groundWidthM, pageSize, orientation, and dpi as the immutable frame, while identifying labels, annotations, styling, overlays, and page elements as editable.

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 and resource: re-export a map bought with make_map, free for 7 days. It distinguishes this from make_map by specifying that it operates on an existing mapId rather than creating a new map.

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

Usage Guidelines4/5

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

It clearly says when this tool applies: re-exporting a previously bought map within the free 7-day window. The frame-immutability rule also implies that changing the frame requires make_map instead, though it does not explicitly name preview_map or check_map as alternatives.

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