outdoorithm

Calculate Drive Times

calculate_drive_times

Read-only

Calculate realistic drive times from an origin to multiple campgrounds using Mapbox routing with live traffic.

Uses the Mapbox Matrix API for traffic-aware routing. Maximum 9 destinations per request.

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": {
      "origin_latitude": "<origin_latitude>",
      "origin_longitude": "<origin_longitude>",
      "destinations": "<destinations>"
    },
    "name": "calculate_drive_times"
  }
}

Input Schema

Name	Required	Description
`destinations`	Yes	List of {campground_id: str, latitude: float, longitude: float} (max 9)
`origin_latitude`	Yes	Latitude of starting location
`origin_longitude`	Yes	Longitude of starting location

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / destinations / description
```
Added value: +"List of {campground_id: str, latitude: float, longitude: float} (max 9)"
```
- addedInput schema / properties / origin_latitude / description
```
Added value: +"Latitude of starting location"
```
- addedInput schema / properties / origin_longitude / description
```
Added value: +"Longitude of starting location"
```
First observedApr 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: the external dependency (Mapbox Matrix API), that results are traffic-aware/live, and the hard cap of 9 destinations per request.

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 tight sentences, front-loaded with the outcome and followed by the implementation/limit detail. No filler.

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?

With an output schema present, return values need no explanation, and the description covers inputs, method, and the 9-destination limit. It could say what happens on over-limit requests or whether failures are per-destination, but nothing essential to a correct call is missing.

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%, covering origin_latitude, origin_longitude, and the destinations item shape. The description repeats the max-9 constraint but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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 ("Calculate realistic drive times"), the input shape (origin to multiple campgrounds), and the mechanism (Mapbox routing with live traffic). No sibling tool offers routing or travel-time computation, so the agent can place it immediately.

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?

Usage is implied by the purpose (call it when you need travel times between a point and campgrounds) but the description never states when to prefer it or what to do when the destination limit is exceeded. No alternatives exist among siblings, so the gap is modest, but there is no explicit guidance.

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

All outdoorithm tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?