Skip to main content
Glama
Mapbox MCP Server

Mapbox MCP Server

Official
by mapbox

Static Map Image Tool

static_map_image_tool
Read-onlyIdempotent

Generates a static map image file from center coordinates, zoom level, size, style, and overlays like markers, paths, or GeoJSON. Use when the user explicitly requests a static image, not an interactive map.

Instructions

Generates a static map image from Mapbox Static Images API. Supports center coordinates, zoom level (0-22), image size (up to 1280x1280), various Mapbox styles, and overlays (markers, paths, GeoJSON). Returns PNG for vector styles, JPEG for raster-only styles. Use only when the user explicitly asks for a static image file — to show a map, use render_map_tool instead, which renders an interactive map.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "center": "<center>",
      "zoom": "<zoom>",
      "size": "<size>"
    },
    "name": "static_map_image_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYesImage size as object with width and height properties in pixels. Each dimension must be between 1 and 1280 pixels
zoomYesZoom level (0-22). Fractional zoom levels are rounded to two decimal places
styleNoMapbox style ID in the format username/style-id (e.g., mapbox/streets-v12, mapbox/satellite-v9, mapbox/dark-v11)mapbox/streets-v12
centerYesCenter point of the map as coordinate object with longitude and latitude properties. Longitude: -180 to 180, Latitude: -85.0511 to 85.0511
overlaysNoArray of overlays to add to the map. Overlays are rendered in order (last item appears on top)
highDensityNoWhether to return a high-density (2x) image

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.18.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.12.6

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds useful context beyond that: the tool talks to an external Mapbox API and returns PNG for vector styles versus JPEG for raster-only styles. It does not discuss rate limits, token/auth requirements, or failure behavior, so it falls short of full behavioral disclosure.

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?

Four sentences, front-loaded with purpose, followed by capabilities, return format, and routing guidance. Each sentence carries information an agent needs, and nothing is wasted.

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 six-parameter tool with nested overlay objects, no output schema, and rich schema descriptions, the description supplies the missing return-format information and the critical sibling routing. Remaining gaps, such as auth requirements or rate-limit behavior against the external API, are relatively minor given the annotation coverage.

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

Parameters3/5

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

Schema description coverage is 100%, with detailed constraints for center, zoom, size, style, overlays, and highDensity. The description only summarizes the same capabilities (center coordinates, zoom 0-22, size up to 1280x1280, styles, overlay types) and adds no syntax or format detail the schema does not already provide. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Generates a static map image from Mapbox Static Images API') and immediately contrasts with the sibling 'render_map_tool', which renders an interactive map. An agent can distinguish the two without opening either schema.

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?

Gives an explicit when-to-use condition ('only when the user explicitly asks for a static image file') and names the alternative for the default case ('to show a map, use render_map_tool instead'). Routing is unambiguous.

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