Skip to main content
Glama

MapIron Maps

Render a static map image

static_map
Read-onlyIdempotent

Render a map as an image (returned inline) with optional pins (markers) and a line (path, e.g. a route). Give center and zoom, or just markers and/or path and the view is fitted automatically. Also returns a reusable image URL for web pages (add your key). Counts 1 static image against the account's monthly cap. Do not use this to show a private address such as someone's home; use privacy_area_map instead.

Input Schema

NameRequiredDescriptionDefault
pathNoA line through these points, in order
zoomNo0 = world, 10 = city, 15 = streets, 18 = buildings
scaleNoPixel density: 2 renders a sharper image for high-density screens at double the pixel size
styleNoMap style: light (default), dark, white or grayscalelight
widthNoImage width in CSS pixels
centerNoMap centre; use with zoom
formatNoImage format. jpg and webp are smaller than pngpng
heightNoImage height in CSS pixels
markersNoPins to draw
paddingNoSpace in pixels kept around markers and paths when the view is fitted automatically
parcelsNoDraw property parcel lines (visible from zoom 13; Growth plans and up). Not available on privacy_area_map
parcel_idNoHighlight one parcel (a parcel_id from parcel_lookup, e.g. us-37183-0794123456); the view fits it if no center is given

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds genuinely new behavior: the image is returned inline, a reusable image URL is also produced (requiring the caller's own key), and each call consumes one static image against a monthly cap. It also flags that parcel rendering needs zoom 13+ and a Growth plan tier. A quota cost and the notion of an inline image plus URL are the kind of facts an agent needs and the annotations cannot convey.

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 tight sentences with no filler, ordered purpose → usage modes → side effects (URL, quota) → exclusion. The exclusion is placed last where it functions as a guard rather than stealing the lead.

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?

For a 12-parameter tool with nested coordinate objects and no output schema, the description covers what comes back (inline image plus URL), the cost model, the tier-gated feature, and the required invocation modes. Nothing an agent needs in order to call it correctly is missing.

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 100%, so the baseline would be 3, but the description adds cross-parameter semantics the schema cannot express: center and zoom form one mode while markers and path trigger automatic view fitting with padding. That interaction meaningfully improves correct invocation beyond the per-field 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?

Opens with a specific verb and resource ("Render a map as an image") and immediately names the optional overlays (pins, path). It also names the sibling it is not (privacy_area_map), so an agent can distinguish it from privacy_area_map 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?

Explicitly states two valid invocation modes (center+zoom, or markers/path with auto-fit) and gives a hard exclusion: do not use for a private home address, use privacy_area_map instead. That is a when-to-use, a when-not-to-use, and a named alternative.

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.