Add a layer (direct)
add_layerAppend 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, ... }. Takes a structured plan; natural-language edits go through mutate_map. The full LayerPlan and Op spec are documented in the MCP resource showmeonmap://docs/workspace-ops-spec.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| intent | No | Optional. 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_id | Yes | map_id from a prior build_map call | |
| layerPlan | Yes | Full LayerPlan object. Must include id, title, source, viz, geometry. | |
| rationale | No | Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments. |