Maps by DeltaBreen

update_style

Idempotent

Change a style's draft: rename it, replace it with a MapLibre style document (style_json), or turn colours and settings on a palette style. Publish afterwards (or pass publish=true) for a new version; earlier versions never change. 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": {
      "style_id": "<style_id>"
    },
    "name": "update_style"
  }
}

Input Schema

Name	Required	Description
`name`	No
`colours`	No	Colour overrides by slot, for palette styles.
`publish`	No	Publish after saving. Default false.
`settings`	No	Numbers, toggles and the font, for palette styles; see create_style.
`style_id`	Yes
`style_json`	No	Replace the draft with this MapLibre style document (an editor export, say). Publish afterwards for a new version.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond annotations, it discloses important behavior: changes apply to the draft, earlier versions never change, and publishing creates a new version. It also states the owner/admin authorization requirement. It does not fully explain partial-update semantics or reversibility, so it is strong but not exhaustive.

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

Conciseness5/5

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

The description is compact and front-loaded: it states the core action, lists supported modifications, then gives publication and authorization details. Every sentence adds useful operational context without waste.

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?

For a six-parameter update tool with nested objects and no output schema, the description covers the main workflows, versioning behavior, publish option, and access requirements. Minor gaps remain around partial versus full replacement semantics, but the essential call context is present.

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?

The description adds meaning beyond the 67%-covered schema: name is for renaming, style_json replaces the draft with a MapLibre document, colours/settings apply to palette styles, and publish=true publishes after saving. Only style_id is left implied, but the key parameters are clarified.

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 states a specific verb and resource ('Change a style's draft') and enumerates the concrete edits: rename, replace via style_json, or adjust colours/settings on a palette style. This clearly distinguishes update_style from siblings like create_style and publish_style.

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 clear context for using the tool: editing a draft, optionally publishing via publish=true, and requiring owner or admin access. It does not explicitly route the agent away from publish_style or explain when not to use this tool, which keeps it below a 5.

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?