Skip to main content
Glama

Make a shareable map

create_map

Make a web map of places, routes or areas, and get a link anyone can open to see it, with no code and no account. Write it as the map document get_map_spec describes. The link works for an hour after the map last changed; opening it, the person can add the map to their squidmaps account to keep it, publish it and share it for good. Returns an id and editToken: keep them, to change this map with update_map rather than making another.

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": {
      "map": "<map>"
    },
    "name": "create_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapYesA squidmaps map document (see get_map_spec): "features" (GeoJSON features, styled with "@" properties), and optionally "name", "description", "basemap", "extent", "view" and "legend", and "customBasemap", for a basemap in its own colors that the person gets with the map.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / map / description
      Previous value: -"A squidmaps map document (see get_map_spec): \"features\" (GeoJSON features, styled with \"@\" properties), and optionally \"name\", \"description\", \"basemap\", \"extent\", \"view\" and \"legend\"."New value: +"A squidmaps map document (see get_map_spec): \"features\" (GeoJSON features, styled with \"@\" properties), and optionally \"name\", \"description\", \"basemap\", \"extent\", \"view\" and \"legend\", and \"customBasemap\", for a basemap in its own colors that the person gets with the map."
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false and destructive=false. Beyond those, the description adds real value: the link expires an hour after the last change, the recipient can claim the map into an account, and id/editToken come back. However, it doesn't say how the editToken must be supplied to update_map, which the agent needs to persist it.

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?

Three tight sentences, front-loaded with what the tool produces, then the format requirement, then the link lifetime and token-retention instruction. No filler wording.

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?

Despite having no output schema, the description states the return values (id and editToken) and the link's expiration and claim behavior. For a single-parameter creation tool with fully covered schema, nothing an agent needs to call it correctly is missing.

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

Parameters5/5

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

Schema coverage is 100% and the nested map object is richly documented, so the schema carries the field-level burden. The description adds the key pointer that the document must be written as get_map_spec describes, which is meaning the schema does not supply.

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?

Names a specific verb and resource ("Make a web map of places, routes or areas") and states the outcome: a link anyone can open, with no code and no account. An agent can distinguish this from update_map/preview_map without reading other schemas.

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?

Explicitly routes follow-up edits to update_map ("keep them, to change this map with update_map rather than making another") and points to get_map_spec for the document format. It does not state when to prefer preview_map over creating a map, so a minor routing gap remains.

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