Skip to main content
Glama
Mapbox MCP Server

Mapbox MCP Server

Official
by mapbox

Convex Hull

convex_tool
Read-onlyIdempotent

Computes the convex hull of points—the smallest convex polygon containing all locations—to bound coverage areas, estimate extent, or wrap location sets offline.

Instructions

Compute the convex hull of a set of points — the smallest convex polygon that contains all the points. Useful for bounding area analysis, estimating coverage area, or wrapping a set of locations. 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": {
      "points": "<points>"
    },
    "name": "convex_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYesPoints to compute the convex hull from (minimum 3)

Output Schema

NameRequiredDescriptionDefault
geometryYesGeoJSON Polygon geometry of the convex hull, or null if hull could not be computed
num_pointsYesNumber of input points used

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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"
  2. First observedv0.12.6

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context — "Works offline without API calls" tells the agent there is no network dependency, latency, or rate-limit concern. It does not discuss degenerate inputs (e.g., collinear points) or output shape, but the output schema covers the latter.

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?

Two sentences, front-loaded with the operation and its definition, then the practical uses and the offline property. Every clause carries information and nothing is repeated.

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 one-parameter, single-purpose geometry tool with rich annotations and an output schema, the description supplies everything needed to select and call it. Only minor edge-case behavior (collinear or duplicate points) is left unstated.

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?

There is a single parameter with 100% schema description coverage, including the minimum-3 constraint, so the schema already carries the semantics. The description's phrase "set of points" and "smallest convex polygon that contains all the points" restates the schema rather than adding format or edge-case guidance.

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+resource ("Compute the convex hull of a set of points") and even defines the geometric concept, so the operation is unambiguous. It stops short of differentiating itself from plausible siblings such as bbox_tool (rectangular bounds) or area_tool, so it falls one step below the top mark.

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?

Three concrete use cases are named (bounding area analysis, coverage-area estimation, wrapping a set of locations), which gives the agent clear context for when to reach for this tool. It never names an alternative or an exclusion, so there is no routing guidance between this and bbox_tool/area_tool.

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