Skip to main content
Glama

Mapbox

by io.github.pipeworx-io

Directions Matrix

directions_matrix
Read-onlyIdempotent

"Distance matrix" / "drive times between multiple points" / "travel times grid" / "all-to-all distances" — N×M distance and duration matrix between many coordinates. Use for traveling-salesman, delivery routing, nearest-warehouse, or "which of these N stores is closest to each of these M customers" questions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNo
sourcesNo
annotationsNo
coordinatesYes
destinationsNo

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
      ],
      [
        -87.6298,
        41.8781
      ]
    ]
  },
  {
    "coordinates": [
      [
        -74.006,
        40.7128
      ],
      [
        -73.9352,
        40.7306
      ],
      [
        -74.006,
        40.758
      ]
    ],
    "destinations": "1;2",
    "profile": "driving",
    "sources": "0"
  }
]
    • changedOutput schema / (root)
      Before
      null
      After
      {
  "description": "Mapbox Directions Matrix API response with distance/time data",
  "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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral context by specifying that the tool returns both distance and duration, and that it constructs an N×M matrix, which goes beyond the annotations and helps the agent understand the output nature.

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?

The description is concise, using two sentences and a list of synonyms to convey the core function, followed by concrete use cases. No unnecessary information is included; every part contributes to understanding the tool's purpose and applicability.

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?

The description covers purpose, use cases, and core behavior well, and an output schema exists to define return values. However, it omits details on optional parameters that affect the matrix semantics, such as how to specify sources/destinations separately. Overall, it is adequately complete for a tool of this complexity, but not exhaustive.

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 must compensate for parameters. It clarifies 'coordinates' as the core input and implies 'sources' and 'destinations' through the N×M matrix concept, but it does not explain 'profile' or 'annotations'. The description adds meaning for the most important parameter but leaves others ambiguous, partially compensating for the schema's lack of descriptions.

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 clearly states the tool computes an N×M distance and duration matrix between coordinates, with synonyms like 'distance matrix' and 'travel times grid'. It distinguishes from the sibling 'directions' tool by focusing on multiple points and all-to-all distances, making the purpose unambiguous.

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 lists specific use cases such as traveling-salesman, delivery routing, and nearest-warehouse problems, effectively indicating when to use this tool. It doesn't explicitly name alternative tools, but the phrase 'between multiple points' implies a contrast with point-to-point routing tools, providing clear context without explicit exclusions.

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