Maps by DeltaBreen

create_style

Create a style and by default publish it, returning a versioned URL that never changes and a latest URL that follows later publishes. Either a built-in look with colour overrides and settings, or a complete MapLibre style document in style_json (an editor export, a file the human pointed you at). Owner or admin.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`base`	No	The built-in look to start from: meadow, midnight, neon, vintage, blueprint or sakura. Default meadow.
`name`	Yes
`colours`	No	Colour overrides by slot: background, earth, water, water_line, landuse (built-up), natural, park, farmland, road (medium), road_highway, road_major, road_minor, road_path, road_outline, road_tunnel, rail, building, boundary, label (cities), label_secondary, label_road, label_water, poi, halo. CSS colours, e.g. "#1f6feb".
`publish`	No	Publish straight away and return the URL a site can use. Default true.
`settings`	No	Numbers, toggles and the font: road_width 0.25-3, road_outline_width 0-3, river_width 0.25-3, label_size 0.5-2, halo_width 0-4, building_opacity 0-1, building_height 0-3, minor_roads_from 10-16, buildings_from 11-16; buildings_3d, road_labels, water_labels, pois, boundaries, show_rail, globe (true/false; globe draws the map on a 3D globe), sky (true/false; paints sky and atmosphere); font: "Noto Sans Regular", "Noto Sans Medium" or "Noto Sans Italic"; language: the label language, e.g. "en", "de", "ja", "zh-Hans" (41 in all), omit for local names.
`style_json`	No	A complete MapLibre style document instead of a look and colours, e.g. one the human made in a style editor and gave you, or a file you read. Its sources, glyphs and sprite are pointed at our tile host when served. Up to 512 KB.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only cover the safety profile (not read-only, not destructive, not idempotent); the description adds meaningful behavior beyond that: publish-by-default, the immutable versioned URL vs. the moving latest URL, the 512 KB size cap, and that sources/glyphs/sprite are repointed at the tile host when served. It stops short of saying what happens on a name collision or a failed publish.

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?

Two sentences, front-loaded with the primary action, default behavior, and return contract, followed by the mode choice and permission note. The second sentence is dense and slightly overstuffed, but every clause carries information.

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?

With no output schema, the description correctly takes on the return-value burden by describing both URLs. For a create tool with a nested settings object and an alternate JSON-document path, the remaining gap is failure/conflict behavior and how name uniqueness is handled.

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 already 83%, so the baseline is 3; the description earns above that by explaining the structural relationship between parameters — base/colours/settings form one mode, style_json is a mutually exclusive alternative. It also characterizes style_json as an editor export or human-provided file, which is semantic guidance the schema does not supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource ('Create a style') with a clear statement of two input modes and the default publish behavior plus return URLs. It does not explicitly distinguish itself from the closely-named siblings update_style and publish_style, which an agent might otherwise confuse with it.

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?

It gives real selection guidance between the two modes: a built-in look with overrides and settings, or a complete MapLibre document in style_json ('an editor export, a file the human pointed you at'). It also states the permission prerequisite ('Owner or admin'). It lacks an explicit 'use update_style instead when modifying an existing style' exclusion.

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

All Maps by DeltaBreen tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?