Mapsource OpenStreetMap & Geospatial APIs

geo_style

Configure semantic basemap styles. Operations: explain and schema retrieve public definitions; intent generates a proposal; preview compiles changes; save, list, revisions, diff, and delete manage profiles. Submit semantic manifests or preset patches, not raw MapLibre JSON. Authenticated operations affect the current key's profiles.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No	diff only: the later revision. Defaults to the current one.
`base`	No	Base preset for the patch. Available presets are listed at /api/styles.	dark
`from`	No	diff only: the earlier revision. Defaults to the one before `to`.
`name`	No	save only: a human name for the profile.
`save`	No	intent only: also save the proposal as a profile revision on this key.
`slug`	No	save and delete: the profile's stable URL id. Defaults to a slug of the name on save.
`patch`	No	Semantic overrides: {"tokens":{...},"typography":{...},"layers":{"roads.motorway":{"color":"#f2a900"}}}. Layer keys come from the explain operation.
`intent`	No	intent: text description of the desired basemap. Returns an editable manifest and a summary of applied changes.
`operation`	No	explain: layer definitions. schema: manifest JSON Schema. intent: generate a style proposal. preview: compile without saving. save: store a profile. list: available presets and profiles. revisions: saved versions. diff: revision comparison. delete: remove a profile.	preview
`description`	No	save: profile description.
`includeStyle`	No	Include the compiled MapLibre style in addition to the hash, diff, and validation issues. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 11, 2026

changedInput schema / properties / base / description

Previous value: -"Preset the patch applies to. Read /api/styles for what each one is."New value: +"Base preset for the patch. Available presets are listed at /api/styles."

changedInput schema / properties / description / description

Previous value: -"save only: what this basemap is for."New value: +"save: profile description."

changedInput schema / properties / includeStyle / description

Previous value: -"Include the full compiled MapLibre style. Off by default because it is large; the hash, diff and issues are usually what you need."New value: +"Include the compiled MapLibre style in addition to the hash, diff, and validation issues. Defaults to false."

changedInput schema / properties / intent / description

Previous value: -"intent only: what the basemap is for, in plain language. The proposal comes back as an editable semantic manifest with the terms it understood and why; the prompt is provenance, not the style."New value: +"intent: text description of the desired basemap. Returns an editable manifest and a summary of applied changes."

changedInput schema / properties / operation / description

Previous value: -"explain: read the semantic layer namespace, free and unauthenticated. schema: the JSON Schema a manifest must satisfy, also free. intent: describe what the basemap is for and get a semantic proposal back. preview: compile a patch and return the hash, diff and issues without saving. save: store the result as a named basemap profile on this key. list: the presets plus profiles saved on this key. revisions: the immutable versions of one profile. diff: what changed between two revisions, in semantic terms. delete: remove a saved profile."New value: +"explain: layer definitions. schema: manifest JSON Schema. intent: generate a style proposal. preview: compile without saving. save: store a profile. list: available presets and profiles. revisions: saved versions. diff: revision comparison. delete: remove a profile."

Changed6 schema fields changedSep 10, 2026

addedInput schema / properties / from

Added value: +{
+  "description": "diff only: the earlier revision. Defaults to the one before `to`.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / intent

Added value: +{
+  "description": "intent only: what the basemap is for, in plain language. The proposal comes back as an editable semantic manifest with the terms it understood and why; the prompt is provenance, not the style.",
+  "maxLength": 2000,
+  "minLength": 3,
+  "type": "string"
+}

changedInput schema / properties / operation / description

Previous value: -"explain: read the semantic layer namespace, free and unauthenticated. preview: compile a patch and return the hash, diff and issues without saving. save: store the result as a named basemap profile on this key. list: the presets plus profiles saved on this key. delete: remove a saved profile."New value: +"explain: read the semantic layer namespace, free and unauthenticated. schema: the JSON Schema a manifest must satisfy, also free. intent: describe what the basemap is for and get a semantic proposal back. preview: compile a patch and return the hash, diff and issues without saving. save: store the result as a named basemap profile on this key. list: the presets plus profiles saved on this key. revisions: the immutable versions of one profile. diff: what changed between two revisions, in semantic terms. delete: remove a saved profile."

changedInput schema / properties / operation / enum

Previous value: -[
-  "explain",
-  "preview",
-  "save",
-  "list",
-  "delete"
-]New value: +[
+  "explain",
+  "schema",
+  "intent",
+  "preview",
+  "save",
+  "list",
+  "revisions",
+  "diff",
+  "delete"
+]

addedInput schema / properties / save

Added value: +{
+  "default": false,
+  "description": "intent only: also save the proposal as a profile revision on this key.",
+  "type": "boolean"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "diff only: the later revision. Defaults to the current one.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

Changed6 schema fields changedSep 9, 2026

addedInput schema / properties / description

Added value: +{
+  "description": "save only: what this basemap is for.",
+  "maxLength": 400,
+  "type": "string"
+}

removedInput schema / properties / explain

Removed value: -{
-  "default": false,
-  "description": "Return the semantic layer namespace and the properties each key accepts, instead of compiling. Use this first when you do not know the keys.",
-  "type": "boolean"
-}

addedInput schema / properties / name

Added value: +{
+  "description": "save only: a human name for the profile.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / operation

Added value: +{
+  "default": "preview",
+  "description": "explain: read the semantic layer namespace, free and unauthenticated. preview: compile a patch and return the hash, diff and issues without saving. save: store the result as a named basemap profile on this key. list: the presets plus profiles saved on this key. delete: remove a saved profile.",
+  "enum": [
+    "explain",
+    "preview",
+    "save",
+    "list",
+    "delete"
+  ],
+  "type": "string"
+}

changedInput schema / properties / patch / description

Previous value: -"Semantic overrides: {\"tokens\":{...},\"typography\":{...},\"layers\":{\"roads.motorway\":{\"color\":\"#f2a900\"}}}. Layer keys come from /api/basemap/contract."New value: +"Semantic overrides: {\"tokens\":{...},\"typography\":{...},\"layers\":{\"roads.motorway\":{\"color\":\"#f2a900\"}}}. Layer keys come from the explain operation."

addedInput schema / properties / slug

Added value: +{
+  "description": "save and delete: the profile's stable URL id. Defaults to a slug of the name on save.",
+  "maxLength": 48,
+  "minLength": 2,
+  "type": "string"
+}

AddedSep 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations, the description discloses the auth scope ('Authenticated operations affect the current key's profiles'), that preview does not persist, that delete removes a profile, and the accepted input format versus raw MapLibre JSON. Note the tension with destructiveHint=false, which sits awkwardly next to a delete operation, though the description itself is explicit rather than misleading.

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?

Purpose is front-loaded in the first sentence, followed by operations, an input constraint, and an auth caveat — a logical order with no filler. It loses a point because the operation list largely restates the schema's enum descriptions verbatim, which is redundant for an agent that can read the schema.

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 an 11-parameter, multi-mode tool with nested patch objects and no output schema, the description covers the operational model, the auth scoping, and the payload format expectation. It stops short of describing return payloads for the read-style operations (explain, schema, list, diff), which an agent would have to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% across 11 parameters, so the schema already carries per-parameter meaning and the operation-to-parameter mapping. The description reinforces the input-format expectation for the patch/manifest payload but adds no new syntax or per-parameter semantics, so baseline 3 applies.

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?

The opening sentence gives a specific verb and resource ('Configure semantic basemap styles'), and the operation enumeration (explain, schema, intent, preview, save, list, revisions, diff, delete) makes the tool's scope unmistakable against catalogue/render siblings. However, it never names or contrasts a sibling tool, so differentiation is implied by scope rather than stated.

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?

Each operation is annotated with its purpose (e.g., 'preview: compile without saving', 'intent: generate a style proposal'), which tells the agent which mode fits a given goal. It also gives a concrete input constraint ('Submit semantic manifests or preset patches, not raw MapLibre JSON'), but provides no explicit when-not-to-use guidance or routing to alternatives like basemap_catalog.

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

All Mapsource OpenStreetMap & Geospatial APIs tools Inspect

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

Need Help?