Skip to main content
Glama

list_style_layers

List everything a MapMap style theme can style: the first-party named bases a style can start from (pass one as create_style's base, or as the static-map API's style=), the named palette slots with their light/dark default colours, the skeleton layer ids (paint order) that set_layer_paint and set_layer_layout accept, what the less obvious layers draw (the footpath layers road-path and road-path-* for footways, cycleways, steps, bridleways, pedestrian streets and tracks, pedestrian squares pedestrian-areas) and the slot that colours each, the OpenMapTiles source-layers extra layers may reference, the insertion slots (bottom, middle, top) an extra layer may name, and the rules for a theme's own sources (your data by https URL). Attribution is enforced on every compiled style and cannot be themed away. Local lookup, no network; always works.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_style_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
basesYesThe first-party named bases a style can start from, in display order: pass one to `create_style`'s `base`, or to the static-map API's `style=`.
slotsYesThe insertion slots an extra layer may name (`"slot"`), bottom of the stack first, with the layer each sits directly below. A layer without a slot goes in `middle`.
sourcesYesThe rules for a theme's own `sources` (customer data by URL).
layer_idsYesThe skeleton layer ids a theme's `layers` may override, in paint order (first = bottom).
attributionYesThe attribution contract: enforced on every compiled style, not themable.
palette_slotsYesThe named palette slots a theme's `palette` may override, with their light/dark defaults, in presentation order.
source_layersYesThe OpenMapTiles source-layers the tiles emit; an extra layer on the `territory` source must reference one of these.
layer_descriptionsYesWhat a layer draws and the palette slot that colours it, for the layers whose id alone does not say (footpaths and pedestrian squares).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
      -  "bases",
      -  "palette_slots",
      -  "layer_ids",
      -  "source_layers",
      -  "attribution"
      -]New value: +[
      +  "bases",
      +  "palette_slots",
      +  "layer_ids",
      +  "layer_descriptions",
      +  "source_layers",
      +  "slots",
      +  "sources",
      +  "attribution"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / $defs / StyleLayerDescription
      Added value: +{
      +  "description": "What one skeleton layer draws.",
      +  "properties": {
      +    "draws": {
      +      "description": "What it draws, in words.",
      +      "type": "string"
      +    },
      +    "layer_id": {
      +      "description": "The skeleton layer id, e.g. \"road-path\".",
      +      "type": "string"
      +    },
      +    "palette_slot": {
      +      "description": "The palette slot that colours it, e.g. \"path\".",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "layer_id",
      +    "palette_slot",
      +    "draws"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / layer_descriptions
      Added value: +{
      +  "default": [],
      +  "description": "What a layer draws and the palette slot that colours it, for the\nlayers whose id alone does not say (footpaths and pedestrian\nsquares).",
      +  "items": {
      +    "$ref": "#/$defs/StyleLayerDescription"
      +  },
      +  "type": "array"
      +}
  3. Changed5 schema fields changed
    • addedOutput schema / $defs / StyleSlotInfo
      Added value: +{
      +  "description": "One insertion slot for extra layers (Mapbox Standard names).",
      +  "properties": {
      +    "before": {
      +      "description": "The skeleton layer id the slot sits directly below.",
      +      "type": "string"
      +    },
      +    "description": {
      +      "description": "Where it sits, in words.",
      +      "type": "string"
      +    },
      +    "slot": {
      +      "description": "`bottom`, `middle` or `top`.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "slot",
      +    "before",
      +    "description"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / $defs / StyleSourcesInfo
      Added value: +{
      +  "description": "What a theme's `sources` block accepts.",
      +  "properties": {
      +    "max_geojson_sources": {
      +      "description": "At most this many of them `geojson`.",
      +      "format": "uint",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "max_sources": {
      +      "description": "At most this many sources per theme.",
      +      "format": "uint",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "types": {
      +      "description": "Accepted source types.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "url_rules": {
      +      "description": "The URL rules every source URL must pass.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "types",
      +    "max_sources",
      +    "max_geojson_sources",
      +    "url_rules"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / slots
      Added value: +{
      +  "default": [],
      +  "description": "The insertion slots an extra layer may name (`\"slot\"`), bottom of\nthe stack first, with the layer each sits directly below. A layer\nwithout a slot goes in `middle`.",
      +  "items": {
      +    "$ref": "#/$defs/StyleSlotInfo"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / source_layers / description
      Previous value: -"The OpenMapTiles source-layers the tiles emit; `extra_layers` must\nreference one of these."New value: +"The OpenMapTiles source-layers the tiles emit; an extra layer on\nthe `territory` source must reference one of these."
    • addedOutput schema / properties / sources
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/StyleSourcesInfo"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The rules for a theme's own `sources` (customer data by URL)."
      +}
  4. Changed3 schema fields changed
    • addedOutput schema / $defs / StyleBaseInfo
      Added value: +{
      +  "description": "One entry in the named-base catalogue (`sn_style::list_bases`).",
      +  "properties": {
      +    "description": {
      +      "description": "One line saying what the base is for. This is what to choose on.",
      +      "type": "string"
      +    },
      +    "group": {
      +      "description": "\"base\" for the two stock slates (`light`, `dark`), \"designed\" for a\ndrawn style.",
      +      "type": "string"
      +    },
      +    "id": {
      +      "description": "Base id: what `create_style`'s `base` and the static-map API's\n`style=` accept, e.g. \"navigator-night\".",
      +      "type": "string"
      +    },
      +    "label": {
      +      "description": "Short display label, e.g. \"Navigator Night\".",
      +      "type": "string"
      +    },
      +    "restrictions": {
      +      "description": "True when the base is drawn to sit under MapMap's\nvehicle-restriction overlay (only `fleet`). That overlay is a\nmapmap.ai runtime layer, not tile data and not part of any compiled\nstyle, so it draws in Studio and on /map and nowhere else. Asking\nfor this base anywhere else gets the palette alone; for a real\nrestriction answer use `check_clearance_on_route` or\n`check_adr_tunnel`, which answer for an actual vehicle.",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "label",
      +    "description",
      +    "group",
      +    "restrictions"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / bases
      Added value: +{
      +  "description": "The first-party named bases a style can start from, in display\norder: pass one to `create_style`'s `base`, or to the static-map\nAPI's `style=`.",
      +  "items": {
      +    "$ref": "#/$defs/StyleBaseInfo"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "palette_slots",
      -  "layer_ids",
      -  "source_layers",
      -  "attribution"
      -]New value: +[
      +  "bases",
      +  "palette_slots",
      +  "layer_ids",
      +  "source_layers",
      +  "attribution"
      +]
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose the key traits: "Local lookup, no network; always works" establishes a side-effect-free, always-available read. It also surfaces a non-obvious constraint, that "Attribution is enforced on every compiled style and cannot be themed away", which affects downstream style work; return format is left to the output schema.

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

Conciseness3/5

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

The lead clause is well front-loaded, but the remainder is one sprawling sentence with eight comma-delimited clauses, including a long parenthetical about footpath layers. Every item is informative, yet the lack of sentence breaks or list structure makes it harder to scan than it needs to be.

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?

An output schema exists, so return values need not be described, and the description still previews the categories returned. For a parameterless discovery tool this is close to complete; only the shape/format of the response is left unstated, which the output schema covers.

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?

Zero parameters, so there is no schema semantics to reinforce; baseline applies. The description still adds value by explaining what the returned identifiers mean in other tools' parameters (base, style=, layer ids, insertion slots).

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?

Opens with a specific verb and resource ("List everything a MapMap style theme can style") and then enumerates the exact catalogues returned: named bases, palette slots, skeleton layer ids, source-layers, insertion slots, and theme source rules. It also distinguishes itself from siblings by naming `create_style`, `set_layer_paint`, and `set_layer_layout` as consumers of the listed values.

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?

Usage is made concrete through cross-references: bases are what you "pass as `create_style`'s `base`, or as the static-map API's `style=`", and layer ids are what "`set_layer_paint` and `set_layer_layout` accept". That tells an agent when to reach for this tool without stating an explicit exclusion or ordering rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources