Skip to main content
Glama

Server Details

Ask in plain English, get a rendered, shareable map from live public data. 24 geospatial tools.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.

Tool Definition Quality

Score is being calculated. Check back soon.

Available Tools

24 tools
add_annotationPlace an annotation on the map (direct)Inspect

Add a user-placed label at a specific coordinate. Annotations are independent of layers and live in their own id namespace. Strict: the id must not already be in use by another CURRENTLY-placed annotation (removed ids can be recycled).

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesStable id for this annotation — caller-supplied.
colorNoOptional CSS color for the marker + label.
labelNoOptional text rendered at the point.
coordsYes[lng, lat] in WGS84.
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
add_fusion_layerAdd bivariate fusion layerInspect

Spatially join two existing layers and add a new layer that encodes both values per region as a 3x3 bivariate choropleth. Both layers must already exist in the workspace (call build_map or add_layer first). Auto-detects the numeric value field from each layer's viz config; pass value_field_a / value_field_b to override. Returns the new layer_id, correlation r, and matched-feature count. Required: map_id, layer_a_id, layer_b_id, rationale.

ParametersJSON Schema
NameRequiredDescriptionDefault
modeNobivariate
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
layer_a_idYes
layer_b_idYes
new_layer_idNo
value_field_aNo
value_field_bNo
add_layerAdd a layer (direct)Inspect

Append a fully-constructed LayerPlan to an existing workspace without going through NL. Pass the same shape the workspace pipeline emits — { id, title, source, viz, geometry, ... }. Prefer this when you already have a structured plan; otherwise use mutate_map. For the full LayerPlan and Op spec, fetch the MCP resource showmeonmap://docs/workspace-ops-spec.

ParametersJSON Schema
NameRequiredDescriptionDefault
intentNoOptional. Which mental model is this add_layer operating under? "primary-data" = the layer the user actually asked to see; "context-overlay" = supporting data layered on top of a primary; "reference-boundary" = admin/geo boundary used as a backdrop; "annotation" = caller-placed callout / pin layer; "comparison" = a layer added to compare against another; "other" = none of the above.
map_idYesmap_id from a prior build_map call
layerPlanYesFull LayerPlan object. Must include id, title, source, viz, geometry.
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
build_mapBuild a mapInspect

Create a new workspace from a natural-language query. Returns a map_id you can pass to mutate_map or get_state for follow-up actions. For the full Op catalog and predicate grammar that downstream tools (mutate_map, filter_layer, etc.) accept, fetch the MCP resource at showmeonmap://docs/workspace-ops-spec — do NOT guess the shapes.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language: "coffee shops in Tokyo", "GDP by country", "volcanoes in Indonesia", etc.
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
clear_filtersClear all filters on a layer (direct, gated)
Idempotent
Inspect

Wipe every predicate currently applied to a layer's filter chain, making every source feature visible again. Inverse of filter_layer. No-op on layers that have no existing filter. GATED: pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYes
layerIdYes
confirmedNoSet to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Wiping a filter chain is recoverable via undo, but autonomous agents lack a UI surface to confirm intent.
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
correlate_layersCompute correlation between two layers
Read-onlyIdempotent
Inspect

Spatially join two existing workspace layers and return the Pearson correlation coefficient r, sample size n, two-sided p-value approximation, plus human-readable strength and direction labels. Pure read — no layer is added, no op is committed, no credit charge. Use this when you want a numeric answer without rendering; use add_fusion_layer when the user wants the visualization. Required: map_id, layer_a_id, layer_b_id, rationale.

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
layer_a_idYes
layer_b_idYes
value_field_aNo
value_field_bNo
export_imageExport map as image
Read-onlyIdempotent
Inspect

Returns a deep-link URL that opens the map in the user's browser and automatically triggers a PNG download. The user clicks the link, the browser renders the map at full resolution with the legend composited (if legend: true), and the file downloads. There is no server-side rendering; the user's browser is the renderer. Required: map_id, rationale. Optional: format (png default), legend (true default).

ParametersJSON Schema
NameRequiredDescriptionDefault
formatNopng
legendNo
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
export_layer_dataExport layer data
Read-onlyIdempotent
Inspect

Export a single layer's features as a downloadable file. Returns a URL with Content-Disposition: attachment so the user's browser downloads it. CSV drops geometry beyond a (lng, lat) centroid — for full polygon/line geometry, use format: "geojson". URL is valid for 24 hours. Required: map_id, layer_id, format, rationale.

ParametersJSON Schema
NameRequiredDescriptionDefault
formatYes
map_idYes
layer_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
export_workspaceExport the workspace JSON
Read-onlyIdempotent
Inspect

Return the current workspace document (ops log + cursor + meta) plus the materialized mapPlan and layerFilters, in a shape suitable for save-to-file / share-by-URL / inspection. Pure read — no mutation, no credit charge. Use this when you want the full raw state for serialization; use get_state when you want the compact envelope for display.

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
filter_layerFilter a layer (direct)Inspect

Narrow a layer to features matching a structured predicate. append:true (default) conjoins with any existing filter; append:false replaces the chain.

ParametersJSON Schema
NameRequiredDescriptionDefault
appendNoDefault true. false replaces the layer's existing filter chain.
intentNoOptional. Which mental model is this filter operating under? "narrow" = generic shrink-the-set; "isolate-outliers" = pull out anomalies for inspection; "compare-subset" = pre-step before a side-by-side compare; "preview-data" = exploratory peek; "other" = none of the above.
map_idYes
layerIdYesid of the layer to filter
predicateYesPredicate in the Mongo-shape grammar. Examples: {op:"eq",field:"category",value:"cafe"}, {op:"gt",field:"magnitude",value:5}, {op:"within",geometry:{type:"Polygon",coordinates:[...]}}, {op:"and",children:[...]}. See docs/superpowers/specs/2026-04-17-workspace-ops-log-design.md §6.
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
get_stateRead map state
Read-onlyIdempotent
Inspect

Return the current workspace, map plan, and active filters for a given map_id.

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
mutate_mapMutate a mapInspect

Apply a natural-language instruction to an existing workspace. Valid mutations: filter a layer, remove a layer, change camera, change basemap. For ambiguous instructions the tool emits a clarification field. For unrelated instructions it emits outOfScope — build a new map in that case. For the full Op catalog and predicate grammar, fetch the MCP resource showmeonmap://docs/workspace-ops-spec.

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYesmap_id from a prior build_map call
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
instructionYese.g., "filter to where magnitude is greater than 5", "change basemap to dark"
query_featuresQuery features from a layer (read-only)
Read-onlyIdempotent
Inspect

Evaluate a predicate against a layer's inline features and return the matching subset. No Op is emitted and the workspace is not mutated. Handy for introspection ("how many X match Y?") before deciding whether to filter, subset, or build a new layer.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoDefault 100, max 1000. Response sets `truncated:true` when clipped.
map_idYes
layerIdYes
predicateYesPredicate in the Mongo-shape grammar. Examples: {op:"eq",field:"category",value:"cafe"}, {op:"gt",field:"magnitude",value:5}, {op:"within",geometry:{type:"Polygon",coordinates:[...]}}, {op:"and",children:[...]}. See docs/superpowers/specs/2026-04-17-workspace-ops-log-design.md §6.
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
redoRedo a previously-undone opInspect

Advance the workspace cursor by one toward the tail of the ops log, replaying the next op that was previously undone. Calling redo when the cursor is already at the tail (no undone ops to fast-forward) fails rather than silently no-op. Note: any new op applied via apply-op / mutate-map after an undo truncates the redo tail (standard edit-stack semantics).

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
remove_annotationRemove an annotation (direct)
Idempotent
Inspect

Drop a previously-placed annotation by id. Strict: removing an already-removed or never-placed id fails. After removal, the id CAN be re-used by a later add_annotation (unlike layer ids, which are tombstoned for the session).

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
annotationIdYes
remove_layerRemove a layer (direct, destructive)
DestructiveIdempotent
Inspect

Drop a layer from the workspace by id. Strict: removing an already-removed or never-added layer fails. Layer ids do NOT recycle — a removed id cannot be re-added later in the same workspace. GATED: this tool is destructive. Pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYes
layerIdYes
confirmedNoSet to true to confirm this destructive action. If omitted or false, the call returns a needs_confirmation envelope. Layer ids are tombstoned — once removed, the same id cannot be re-added later in this workspace.
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
rename_layerRename a layer (direct)
Idempotent
Inspect

Change a layer's id from oldLayerId to newLayerId. Re-keys any existing filter chain and preserves insertion order among sibling layers. Strict: newLayerId must not already be in use (current OR tombstoned) in this workspace. Subsequent ops must reference the layer by its new id.

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
newLayerIdYesNew id. Must be unique within the workspace.
oldLayerIdYes
report_blockerReport a blocker (agent feedback)
Read-onlyIdempotent
Inspect

Tell the ShowMeOnMap team your agent hit something it could not accomplish — an unsupported intent, a missing tool, an unclear schema, an op that failed in a confusing way. Use this when build_map / mutate_map / a direct-op tool returns something you cannot recover from, OR when you would have wanted a different tool to exist. Records the report to a server-side log; does not unblock the current session, but feeds future capability work. No map_id required — file the report even if no map was built.

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idNoOptional. The map_id you were working on, if any.
what_i_triedYesWhich tools / inputs you attempted, in order. Be specific — tool name + key arg shape is ideal.
what_i_was_tryingYesHigh-level intent in one or two sentences. e.g. "merge two filtered choropleths into a fused bivariate map".
where_i_got_stuckYesThe specific failure: what came back, what was missing, why you could not proceed.
suggested_capabilityNoOptional. A new tool, op, or schema field that would have unblocked you.
restyle_layerRestyle a layer (direct)
Idempotent
Inspect

Adjust a layer's color and/or opacity. Within-palette changes only — the renderer silently ignores fields the current viz variant doesn't support. Pass at least one of color / opacity; passing neither is an accepted no-op.

ParametersJSON Schema
NameRequiredDescriptionDefault
colorNoCSS color string: hex (#RRGGBB), rgb/rgba, or named color.
map_idYes
layerIdYes
opacityNo0 (transparent) to 1 (opaque).
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
select_withinSubset a layer to a polygon selection
Read-onlyIdempotent
Inspect

Create a new layer containing the source layer's features that lie within the supplied polygon. The source layer is untouched. Useful for "show me only the X inside this country/bbox/hand-drawn shape."

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
selectionYesGeoJSON Polygon or MultiPolygon in [lng,lat] coordinate order.
newLayerIdYesId for the new layer. Must not already be in use in this workspace.
inheritStyleNoDefault true. false emits a new layer with minimal default styling.
sourceLayerIdYes
set_cameraSet the map camera (direct)
Idempotent
Inspect

Override the workspace camera. Latest set_camera op wins during replay. Two modes: fitBounds with a [w,s,e,n] bbox (plus optional padding/animateMs), or flyTo with [lng,lat] center + zoom (plus optional pitch/bearing/animateMs). Use for "zoom to Japan", "center on Paris at z=10", or finishing a drill-down after filter_layer. Equivalent to the camera move mutate_map would emit, but skips the NL roundtrip.

ParametersJSON Schema
NameRequiredDescriptionDefault
cameraYes
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
set_timeSet the time window (direct)
Idempotent
Inspect

Override the current time-range filter. Latest set_time op wins during replay. Use for "filter to 2020-2024" or "show only the last 7 days" intents. Not yet consumed by the renderer — the UI drives the slider directly — but the value is captured in the ops log and queryable via get_state.

ParametersJSON Schema
NameRequiredDescriptionDefault
fieldYesFeature property carrying the time value (e.g. "date", "year", "timestamp").
formatNoHow rangeStart/rangeEnd encode time. Default: unix_ms at render time.
map_idYes
rangeEndYesInclusive upper bound of the visible window.
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
rangeStartYesInclusive lower bound of the visible window.
tagSave a named checkpoint (direct)Inspect

Label the current workspace state with a user-supplied name. The label is mirrored into workspace.meta.tags so UIs can render a named-revision history. Tagging the same label twice is idempotent — no error, no duplicate entry.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesCheckpoint label, e.g. "before EV layer added" or "v1.0".
map_idYes
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.
undoUndo the most recent op (gated)Inspect

Rewind the workspace cursor by one, re-materializing the state as it was before the last mutation. Does NOT delete any ops — redo will fast-forward. Calling undo at the workspace genesis (cursor === 0, only the CreateWorkspace op is in scope) is a no-op that surfaces an error rather than silently doing nothing. GATED: pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.

ParametersJSON Schema
NameRequiredDescriptionDefault
map_idYes
confirmedNoSet to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Autonomous undo without user intent is a footgun — an agent that decides to "fix" something can erase prior work.
rationaleYesShort audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources