Skip to main content
Glama

Mapbox

by io.github.pipeworx-io

Directions

directions
Read-onlyIdempotent

"Directions from A to B" / "how long does it take to drive from X to Y" / "how far is [A] from [B]" / "walking / cycling / driving directions" / "navigation between points" / "shortest route" — turn-by-turn routing between two or more coordinates. Returns geometry, distance (meters), duration (seconds), voice + banner instructions, and alternatives. Profile: driving, driving-traffic, walking, or cycling. Backed by Mapbox's commercial-grade traffic data and global road network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepsNo
profileNo
languageNo
overviewNo
geometriesNo
annotationsNo
coordinatesYes
alternativesNo
voice_instructionsNo
banner_instructionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      [
  {
    "coordinates": [
      [
        -122.4194,
        37.7749
      ],
      [
        -118.2437,
        34.0522
      ]
    ]
  },
  {
    "coordinates": [
      [
        -74.006,
        40.7128
      ],
      [
        -73.9352,
        40.7306
      ]
    ],
    "language": "en",
    "profile": "walking",
    "steps": true
  }
]
    • changedOutput schema / (root)
      Before
      null
      After
      {
  "description": "Mapbox Directions API response with routing information",
  "type": "object"
}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds context about the underlying Mapbox data, supported profiles (driving, walking, cycling), and returned elements (alternatives, banner/voice instructions), all consistent with annotations.

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 concise, information-dense sentences cover trigger examples, core functionality, return types, profiles, and data source. There is no fluff or redundancy; every clause adds value.

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?

Given the output schema enriches return expectations and annotations cover safety, the description is largely adequate for selecting and invoking the tool. Some optional parameters are not explained, but the core invocation (coordinates, profile) is clear, and the examples in the schema provide additional usage patterns.

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?

With 0% schema description coverage, the description partially compensates by explaining coordinates, profile, alternatives, and voice/banner instructions. However, parameters like steps, overview, geometries, annotations, and language remain undocumented in both schema and description, leaving gaps.

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?

The description explicitly states 'turn-by-turn routing between two or more coordinates' and lists concrete output types (geometry, distance, duration, voice/banner instructions). It opens with natural-language trigger examples that clearly define the tool's purpose and distinguish it from the sibling directions_matrix.

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?

The description provides clear when-to-use signals through example queries ('Directions from A to B', 'how long does it take to drive from X to Y'). It does not explicitly exclude alternatives like directions_matrix, but the context strongly implies this is the tool for point-to-point routing.

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

All Mapbox toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Many tools have overlapping purposes (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) and several tools serve similar data-retrieval functions, making it difficult for an agent to distinguish which to use.

Naming Consistency4/5

Tool names mostly follow a consistent verb_noun pattern (e.g., geocode_forward, generate_llms_txt, resolve_entity). A few less descriptive names (forget, recall) exist but overall naming is predictable.

Tool Count2/5

38 tools is far too many for a server branded as 'Mapbox'. Only about 8 tools directly relate to map/geospatial functionality; the rest are unrelated (Pipeworx data, Polymarket, memory). The scope is dramatically overextended.

Completeness2/5

The Mapbox-specific tools lack coverage of major features like style management, tilesets, or data upload. The non-Mapbox tools cover their domains moderately, but the server's overall completeness for its named purpose (Mapbox) is severely lacking.

Resources