Skip to main content
Glama
atlasfetch-mcp

atlasfetch-mcp

Official

Move or reshape a boundary, keeping its name and properties

update_boundary
DestructiveIdempotent

Replace the shape of ONE existing boundary. Its id, name, properties and set stay as they are, so every lookup that matches it keeps returning the same properties.

Instructions

Replace the shape of ONE existing boundary. Its id, name, properties and set stay as they are, so every lookup that matches it keeps returning the same properties.

Use this to fix or move a zone. Do NOT delete it and add it again: that gives it a new id and loses the properties unless they are re-sent.

Name the boundary by set and name; this finds its id. If a set holds two boundaries with that name, the answer lists their ids and asks for one. The new shape gets the same checks as add_boundary, including the 50-point cap (refused, unbilled). Only boundaries on this account can be changed.

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": {
      "set": "<set>",
      "geometry": "<geometry>"
    },
    "name": "update_boundary"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe boundary’s id (a UUID), when it is known. Use this or name.
setYesThe set the boundary is in.
nameNoThe boundary’s name. Use this or id.
geometryYesThe new shape: a GeoJSON Polygon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, but the description goes further: it explains what survives the replacement (identity and properties), how ambiguous name resolution behaves (ids returned, caller asked to pick one), the 50-point cap, that a rejected shape is unbilled, and the account boundary. That is exactly the context annotations cannot carry.

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?

Five short sentences, front-loaded with the operation and its invariant (id/name/properties preserved), then the when-to-use, then the error path. No sentence restates the name or title without adding 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?

For a mutation with a nested GeoJSON payload and no output schema, the description covers validation limits, ambiguity handling and preservation semantics. The one gap is what a successful call returns or how to confirm the new shape landed, which the agent has to discover at runtime.

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 resolving semantics beyond the schema: naming by set+name performs an id lookup, and duplicate names produce an id list rather than an arbitrary pick. It does not add syntax detail for the geometry rings, which is left entirely to the schema.

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 ('Replace the shape of ONE existing boundary') and immediately scopes it by what is preserved: id, name, properties, set. The capitalization of ONE disambiguates it from bulk or create operations, so an agent can tell it apart from add_boundary without opening either schema.

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 the positive case ('Use this to fix or move a zone') and an explicit anti-pattern with the reason ('Do NOT delete it and add it again: that gives it a new id and loses the properties'). It also states the account restriction ('Only boundaries on this account can be changed'), leaving nothing to inference.

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