Skip to main content
Glama

add_layer

Add a MapLibre source and layers to a map to display raster or vector geospatial data.

Instructions

Add a MapLibre source and one or more layers. Maps to map.addSource() and map.addLayer().


📚 AVAILABLE DATA LAYERS & USAGE CONTEXT

Available Data Layers

You have access to map visualization tools that can display geospatial data layers.

Note: These layer definitions can be customized by setting the MCP_MAP_SYSTEM_PROMPT environment variable with your own layer information.

Base Layers (Raster)

OpenStreetMap Standard

  • ID: osm

  • Type: Raster

  • URL: https://tile.openstreetmap.org/{z}/{x}/{y}.png

  • Attribution: © OpenStreetMap contributors

  • Description: Standard OpenStreetMap tiles with streets, labels, and geographic features

OpenStreetMap Humanitarian

  • ID: osm-humanitarian

  • Type: Raster

  • URL: https://tile-{s}.openstreetmap.fr/hot/{z}/{x}/{y}.png

  • Subdomains: a,b,c

  • Attribution: © OpenStreetMap contributors, Tiles courtesy of Humanitarian OpenStreetMap Team

  • Description: High-contrast humanitarian style, good for overlaying data

CartoDB Positron (Light)

  • ID: carto-light

  • Type: Raster

  • URL: https://{s}.basemaps.cartocdn.com/light_all/{z}/{x}/{y}{r}.png

  • Subdomains: a,b,c,d

  • Attribution: © OpenStreetMap contributors © CARTO

  • Description: Light grayscale base map, excellent for data visualization

Esri World Imagery

  • ID: esri-satellite

  • Type: Raster

  • URL: https://server.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer/tile/{z}/{y}/{x}

  • Attribution: Tiles © Esri

  • Description: High-resolution satellite imagery

Vector Data Layers

World Database on Protected Areas (WDPA)

  • ID: wdpa

  • Type: Vector

  • URL: pmtiles://https://s3-west.nrp-nautilus.io/public-wdpa/WDPA_Dec2025.pmtiles

  • Source Layer: wdpa

  • Description: Global protected areas dataset with IUCN categorization and management information

Attributes:

  • IUCN_CAT: IUCN management category (Ia=Strict Nature Reserve, Ib=Wilderness Area, II=National Park, III=Natural Monument, IV=Habitat Management, V=Protected Landscape, VI=Sustainable Use)

  • OWN_TYPE: Ownership type (State, Private, Community, etc.)

  • ISO3: ISO 3166-1 alpha-3 country code

  • STATUS_YR: Year of establishment or designation

  • NAME: Protected area name

  • DESIG_ENG: Designation in English (e.g., National Park, Wildlife Sanctuary)

Overture Maps - Administrative Boundaries

  • ID: overture-admins

  • Type: Vector

  • URL: pmtiles://https://overturemaps.azureedge.net/release/2024-11-13.0/theme=admins.pmtiles

  • Source Layer: admins

  • Description: Administrative boundary polygons including countries, states/regions, and counties

Attributes:

  • admin_level: Administrative level (2=country, 4=state/region, 6=county)

  • names: Name information in multiple languages

  • iso_country_code_alpha_2: ISO country code

  • iso_sub_country_code: Sub-country codes

Overture Maps - Places

  • ID: overture-places

  • Type: Vector

  • URL: pmtiles://https://overturemaps.azureedge.net/release/2024-11-13.0/theme=places.pmtiles

  • Source Layer: places

  • Description: Points of interest including businesses, landmarks, and facilities

Attributes:

  • categories: Category classification

  • names: Place names in multiple languages

  • confidence: Data confidence score

Natural Earth Countries (50m)

  • ID: ne-countries

  • Type: Vector

  • URL: pmtiles://https://cdn.protomaps.com/data/ne-50m-countries.pmtiles

  • Source Layer: countries

  • Description: Country boundaries at 1:50m scale from Natural Earth

Attributes:

  • NAME: Country name

  • ISO_A2: ISO Alpha-2 country code

  • POP_EST: Population estimate

  • GDP_MD: GDP in millions USD

  • CONTINENT: Continent name

Example Usage Patterns

Create a base map:

{
  "tool": "add_layer",
  "arguments": {
    "id": "osm-base",
    "type": "raster",
    "source": {
      "type": "raster",
      "tiles": ["https://tile.openstreetmap.org/{z}/{x}/{y}.png"],
      "attribution": "© OpenStreetMap contributors"
    }
  }
}

Add protected areas in a specific country:

{
  "tool": "add_layer", 
  "arguments": {
    "id": "wdpa",
    "type": "vector",
    "source": {
      "type": "vector",
      "url": "pmtiles://https://s3-west.nrp-nautilus.io/public-wdpa/WDPA_Dec2025.pmtiles"
    },
    "layers": [{
      "id": "wdpa-fill",
      "type": "fill",
      "source": "wdpa",
      "source-layer": "wdpa",
      "paint": {"fill-color": "green", "fill-opacity": 0.5}
    }]
  }
}

Filter to specific country (e.g., USA):

{
  "tool": "filter_layer",
  "arguments": {
    "layer_id": "wdpa",
    "filter": ["==", ["get", "ISO3"], "USA"]
  }
}

Style by attribute (e.g., IUCN category):

{
  "tool": "set_layer_paint",
  "arguments": {
    "layer_id": "wdpa",
    "property": "fill-color",
    "value": [
      "match",
      ["get", "IUCN_CAT"],
      "II", "#2ca02c",
      "IV", "#1f77b4", 
      "V", "#ff7f0e",
      "#999999"
    ]
  }
}

Tips for Layer Selection

  • Always start with a base layer (OSM, CartoDB, or Esri)

  • Use light base maps (carto-light) when overlaying lots of data

  • Use satellite imagery (esri-satellite) for environmental or geographic context

  • PMTiles sources are efficient for large vector datasets

  • Filter by geography first (ISO3, admin_level) to improve performance

  • Use meaningful colors and opacity for multiple overlapping layers


Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique identifier for the source and logical layer.
typeYesThe type of data source.
stateNoOptional initial map state JSON string.
layersNoArray of MapLibre layer objects. If omitted for 'raster', a default layer is created.
sourceYesMapLibre source configuration (e.g. {type: 'vector', url: '...'})
visibleNoInitial visibility.
session_idNoSession ID (default: 'default')
Behavior4/5

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

With no annotations, the description carries the full burden and does well by disclosing API mapping, default layer creation ('If omitted for "raster", a default layer is created'), and providing extensive data source context. It does not cover id conflict behavior or other side effects, so it falls short of a 5.

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?

The description is long, but well-structured with headers, tables, and code blocks that make it scannable. The opening sentence is succinct and front-loaded. The reference material is necessary for correct invocation, though it could be seen as verbose.

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?

The tool is complex (7 params, nested objects) with no annotations or output schema, yet the description covers purpose, usage patterns, and available data layers comprehensively, including example invocations and selection tips. Gaps remain around duplicate ids and error handling, but overall it is sufficient for correct selection and invocation.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds significant value through concrete JSON examples for source, layers, and id, plus a catalog of valid data layers with attributes and URLs. This goes far beyond the schema's simple descriptions, effectively teaching the agent how to structure parameters.

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?

The description clearly states 'Add a MapLibre source and one or more layers' and explicitly maps to `map.addSource()` and `map.addLayer()`. This specific verb+resource pairing distinguishes it from sibling tools like remove_layer and filter_layer.

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

Usage Guidelines4/5

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

The description provides 'Example Usage Patterns' showing when to use add_layer for base maps and data layers, and points to filter_layer and set_layer_paint for subsequent operations. Tips like 'Always start with a base layer' imply usage context. It lacks explicit 'when not to use' statements, but the workflow is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/boettiger-lab/mcp-map-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server