Skip to main content
Glama

Change a map

update_map
DestructiveIdempotent

Change a map made with create_map when the person asks for changes, keeping its link: anyone who has the link sees the change, and it keeps working another hour. Send the whole changed map document, not just what changed: it replaces the map. Fails once someone has added the map to their account.

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": {
      "id": "<id>",
      "editToken": "<editToken>",
      "map": "<map>"
    },
    "name": "update_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe map's id, from create_map
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.
editTokenYesThe editToken from create_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.8/5.0
Behavior5/5

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

Annotations only flag destructive/openWorld/idempotent; the description explains what that destructiveness means in practice — the payload replaces the map rather than patching it — and adds link-preservation behavior (the same link shows the change and stays valid another hour). It also discloses the precondition under which the call errors, which no annotation conveys.

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 sentences, each carrying distinct load-bearing information: the action, the replacement rule, and the failure condition. The most consequential constraint (full document, not a patch) is front-loaded before the failure note.

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?

Covers action, replacement semantics, link behavior, and failure mode for a nested-object mutation tool with no output schema. The only small gap is what the response contains after a successful edit (e.g., whether it echoes the map or link), which an agent must discover by calling.

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 real semantics for the "map" parameter: it must be the complete document, not a diff, because it replaces existing content. The id/editToken parameters are left to the schema, which documents them as coming from create_map.

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 ("Change a map") and anchors it to the sibling that produced the map (create_map), so an agent can tell it apart from create_map and preview_map without opening any schema. The scope of what is being modified (the whole map document at an existing link) is stated immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ("when the person asks for changes"), an explicit usage rule ("Send the whole changed map document, not just what changed"), and an explicit failure condition ("Fails once someone has added the map to their account"). That is when-to-use, how-to-call, and when-it-won't-work in three sentences.

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