Mapsource OpenStreetMap & Geospatial APIs

geo_render

Read-only

Render a static PNG map from a center and zoom or bounding box. Supports GeoJSON overlays, result handles, and up to 50 labeled markers. Dark and light styles use raster rendering; other preset or profile names use vector rendering. Requires a subscription key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	No
`lon`	No
`bbox`	No	[west, south, east, north]. Fits the viewport to this instead of using lat/lon/zoom.
`zoom`	No
`pitch`	No	Vector renders only.
`style`	No	dark or light composites the raster basemaps. Any other value names a style preset or one of your saved basemap profiles and is rendered as vector against that compiled style.	dark
`width`	No
`height`	No
`bearing`	No	Vector renders only.
`geojson`	No	GeoJSON to draw, or a result handle such as rh_ followed by 32 hex characters.
`markers`	No
`styleRevision`	No	Saved profile revision to use for rendering.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 11, 2026

changedInput schema / properties / styleRevision / description

Previous value: -"Pin the render to an immutable revision of a saved profile, so the same call renders the same image after the profile is edited."New value: +"Saved profile revision to use for rendering."

Changed1 schema field changedSep 10, 2026

addedInput schema / properties / styleRevision

Added value: +{
+  "description": "Pin the render to an immutable revision of a saved profile, so the same call renders the same image after the profile is edited.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

Changed1 schema field changedSep 10, 2026

changedInput schema / properties / geojson / description

Previous value: -"GeoJSON to draw, or a result handle such as res_abc123."New value: +"GeoJSON to draw, or a result handle such as rh_ followed by 32 hex characters."

Changed6 schema fields changedSep 9, 2026

addedInput schema / properties / bearing

Added value: +{
+  "default": 0,
+  "description": "Vector renders only.",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}

addedInput schema / properties / pitch

Added value: +{
+  "default": 0,
+  "description": "Vector renders only.",
+  "maximum": 60,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / style / description

Added value: +"dark or light composites the raster basemaps. Any other value names a style preset or one of your saved basemap profiles and is rendered as vector against that compiled style."

removedInput schema / properties / style / enum
```
Removed value: -[
-  "dark",
-  "light"
-]
```
addedInput schema / properties / style / maxLength
```
Added value: +64
```
addedInput schema / properties / style / minLength
```
Added value: +1
```

AddedSep 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: the style-dependent rendering mode (dark/light = raster, any other name = vector) and the subscription-key auth requirement, both of which an agent needs to call it successfully.

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?

Four tight sentences, front-loaded with the core purpose before capabilities, rendering behavior, and the auth requirement. No filler; each sentence carries a distinct fact.

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?

With no output schema and 12 parameters at 50% coverage, the description covers purpose, capabilities, render modes, and auth well. Minor gaps remain on default dimensions and how overlays interact with the center/bbox inputs, but nothing essential to invoking it correctly is missing.

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 50%, and much of what the description says about parameters (GeoJSON, result handles, up to 50 markers, style modes) is already present in the schema. It adds little syntax or format detail for the undocumented parameters (width, height, lat/lon, zoom), so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Render a static PNG map') plus the two input modes (center/zoom or bounding box), so the agent knows exactly what it produces. It is clearly distinct from siblings like geo_analyze or route, but it never names or contrasts an alternative explicitly, keeping it short of a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the description explains the raster-vs-vector rendering rule and the subscription-key prerequisite, which helps an agent know when the tool behaves differently. However, there is no explicit when-to-use vs when-to-pick-another-sibling guidance, so it lands at minimum-viable.

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

All Mapsource OpenStreetMap & Geospatial APIs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?