Skip to main content
Glama

MapMap

by ai.mapmap
OverviewDiscussionsAdmin

create_style

Create a hosted map style. Provide a name, optionally a named base to start from (light, dark, streets, midnight, navigator-day, navigator-night, fleet, outdoor, dataviz, backdrop, print - call list_style_layers for what each one is for), and optionally a theme document ({base: "light"|"dark", palette: {slot: colour}, layers: {layer_id: overrides}}). The named base is laid down first and the theme document is merged over it, so "streets with darker water" is one call; with neither, the style starts from the default theme. A theme may also set worldview (ISO 3166-1 alpha-2, accepted: AE, KR, SA, US) to display that jurisdiction's official names for a small curated registry of renamed features; omitted, labels keep the OSM on-the-ground names. Returns the generated style_id (pass it to set_palette / set_layer_paint) and the compiled style URL for MapLibre.

Input Schema

NameRequiredDescriptionDefault
baseNoOptional named base to start from, e.g. "streets", "midnight", "navigator-night", "fleet". Call `list_style_layers` for the catalogue, including which bases expect an overlay of their own. The base's whole document is laid down first and `theme` is merged over it, so a base plus two palette entries is a complete style. Omitted, the style starts from the default light theme as it always did.
nameYesHuman-readable style name; its kebab-case slug seeds the style id.
themeNoOptional theme document (palette/layer overrides). Merged over `base` when one is given; on its own, it replaces the default theme outright.

Output Schema

NameRequiredDescriptionDefault
themeYesThe theme document that was stored.
versionYesThe published version (always 1 on create).
style_idYesThe generated style id, pass it to `set_palette`, `set_layer_paint` and `get_style`.
style_urlYesImmutable URL of the compiled style at this version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / style_id / description
      Previous value: -"The generated style id — pass it to `set_palette`,\n`set_layer_paint` and `get_style`."New value: +"The generated style id, pass it to `set_palette`,\n`set_layer_paint` and `get_style`."
  2. Changed2 schema fields changed
    • addedInput schema / properties / base
      Added value: +{
+  "description": "Optional named base to start from, e.g. \"streets\", \"midnight\",\n\"navigator-night\", \"fleet\". Call `list_style_layers` for the\ncatalogue, including which bases expect an overlay of their own. The\nbase's whole document is laid down first and `theme` is merged over\nit, so a base plus two palette entries is a complete style. Omitted,\nthe style starts from the default light theme as it always did.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedInput schema / properties / theme / description
      Previous value: -"Optional theme document (palette/layer overrides). Omitted, the\nstyle starts from the default theme carrying `name`."New value: +"Optional theme document (palette/layer overrides). Merged over\n`base` when one is given; on its own, it replaces the default theme\noutright."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full disclosure and does it well: it describes merge precedence (base laid down first, theme merged over), the no-argument default theme, and the worldview side effect on label naming. It does not cover persistence/ownership or any auth requirements for a 'hosted' write, leaving a small gap.

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?

Front-loads the purpose in the first sentence and then packs merge semantics, defaults, worldview, and return values into one dense paragraph. It is on the long side and could be split, but nearly every clause carries information an agent needs.

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

Completeness5/5

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

Given a write tool with no annotations and an output schema present, the description supplies everything needed to invoke it correctly: required vs optional inputs, composition/merge rules, default behavior, worldview options, and the returned style_id/URL chain to sibling tools.

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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning: it enumerates the concrete base names (light, dark, streets, midnight, navigator-day, fleet, outdoor, dataviz, backdrop, print), spells out the theme document shape (base/palette/layers with slot: colour semantics), and gives the accepted worldview codes with their effect on labels.

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?

States a specific verb and resource ('Create a hosted map style') and immediately distinguishes itself from siblings like get_style, set_palette, set_layer_paint by describing creation plus what it returns. An agent can tell this is the style-creation entry point without reading further.

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?

Explains the composing cases clearly: base alone, theme alone, base+theme combined ('streets with darker water is one call'), and neither (default theme). It also points to list_style_layers for the catalogue and names set_palette/set_layer_paint as the follow-up tools. It stops short of stating explicit exclusions such as when to modify an existing style instead of creating one.

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

All MapMap toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources