Skip to main content
Glama

filter_layer

Apply a MapLibre filter expression to a map layer and its sub-layers, showing only features that match the specified attribute conditions.

Instructions

Apply a MapLibre filter expression to a layer and all its sub-layers.


📚 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
stateNoOptional map state JSON string.
filterYesMapLibre filter expression (e.g. ['==', 'property', 'value'])
layer_idYesThe ID of the layer to filter.
session_idNoThe session ID.
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. It does mention that the filter applies to 'all its sub-layers,' which is useful, but it fails to disclose whether the filter replaces an existing filter, whether the operation is reversible, or any side effects. The description is largely filled with layer catalog information rather than behavior of the tool itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is concise, but the description is dominated by a lengthy 'AVAILABLE DATA LAYERS & USAGE CONTEXT' block that is largely unrelated to the filter tool's specific operation. This boilerplate could be shortened or moved to a shared system prompt. The core tool explanation is padded with extensive examples and tips that are not all necessary for using filter_layer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides rich context about available data layers and their attributes, which is essential for constructing filters. It also gives example usage and tips. However, it omits important behavioral details (replacement semantics, reversibility) and does not describe return values or error cases. For a simple tool with no output schema, the description is functional but not completely self-sufficient.

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 description coverage is 100%, giving basic meaning for layer_id and filter. The description adds significant value by providing attribute names (e.g., ISO3, admin_level) and a concrete example filter expression (["==", ["get", "ISO3"], "USA"]), which helps the agent construct valid filters beyond the schema's generic description.

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 opens with 'Apply a MapLibre filter expression to a layer and all its sub-layers,' which is a specific verb+resource statement that clearly distinguishes it from sibling tools like add_layer, set_layer_paint, and remove_layer. The purpose is unmistakable and actionable.

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 includes example usage patterns and tips such as 'Filter by geography first (ISO3, admin_level) to improve performance,' which provide practical context for when to use the filter tool. It also contrasts filtering with styling through separate examples (filter_layer vs set_layer_paint), though it does not explicitly name alternatives or exclusions.

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