Skip to main content
Glama
Mapbox MCP Server

Mapbox MCP Server

Official
by mapbox

Create Buffer Zone

buffer_tool
Read-onlyIdempotent

Create a buffer zone polygon around a point, line, or polygon at a specified distance for proximity analysis, service areas, or zones of influence. Works offline without API calls.

Instructions

Create a buffer zone (polygon) around a point, line, or polygon at a specified distance. Useful for proximity analysis, service areas, or creating zones of influence. Works offline without API calls.

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": {
      "geometry": "<geometry>",
      "distance": "<distance>"
    },
    "name": "buffer_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsNoUnit of measurement for distancekilometers
distanceYesBuffer distance
geometryYesGeometry coordinates (Point, LineString, or Polygon)

Output Schema

NameRequiredDescriptionDefault
unitsYes
distanceYes
bufferedPolygonYesBuffer polygon as array of rings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.18.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / properties / bufferedPolygon / items / items / items
      Previous value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]New value: +false
    • addedOutput schema / properties / bufferedPolygon / items / items / maxItems
      Added value: +2
    • addedOutput schema / properties / bufferedPolygon / items / items / minItems
      Added value: +2
    • addedOutput schema / properties / bufferedPolygon / items / items / prefixItems
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "number"
      +  }
      +]
  2. First observedv0.12.6

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely extra behavioral note (offline, no API calls) but says nothing about buffer resolution/vertex density, geodesic vs planar computation, or how large distances behave. With annotations carrying most of the load, a 3 is appropriate.

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?

Three short sentences, front-loaded with the core action and resource, with no wasted wording. The middle sentence is the least essential but does supply usage context, so trimming is minor rather than needed.

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?

An output schema exists, so the description need not explain the returned polygon, and the annotations cover safety and idempotency. What remains is minor: coordinate order is only stated in the schema, and semantics like distance units applying to the output geometry are not spelled out. For a simple three-parameter geometry tool this is close to sufficient.

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% and both required parameters (geometry, distance) plus the units enum are documented in the schema itself. The description only restates that distance is specified and that geometry may be point, line, or polygon, which is largely redundant with the schema. Baseline 3 applies when the schema does the heavy lifting.

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 description gives a specific verb and resource ("Create a buffer zone (polygon)") and states the accepted geometry types and the distance parameter, so the agent immediately knows what the tool produces. It does not name any sibling (e.g., isochrone_tool or convex_tool) to differentiate against, which keeps it just below a top score.

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

Usage Guidelines3/5

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

It offers situational context ("proximity analysis, service areas, or zones of influence") and one useful constraint ("works offline without API calls"), which nudges the agent toward it for local geometry work. There is no explicit when-not guidance or pointer to alternatives such as a travel-time isochrone for reachability questions, so selection versus siblings is only implied.

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