Skip to main content
Glama

outdoorithm

by io.github.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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destinationsYesList of {campground_id: str, latitude: float, longitude: float} (max 9)
origin_latitudeYesLatitude of starting location
origin_longitudeYesLongitude of starting location

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed4 schema fields changed
    • 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"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate a read-only, non-destructive operation. The description adds behavioral context by mentioning the use of the Mapbox Matrix API, incorporation of live traffic, and a cap of 9 destinations per request. These details go beyond the annotations, though it does not discuss error handling or broader rate limits.

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?

The description is relatively concise and front-loaded, with the main purpose in the first sentence. However, it redundantly mentions traffic-awareness ('live traffic' and 'traffic-aware') in the second sentence, which could be trimmed without losing meaning.

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 return values are covered elsewhere. The description sufficiently explains the tool's purpose, method, and a key limitation (max 9 destinations). For a read-only calculation tool with simple parameters, this is adequate even though it omits edge-case handling or prerequisites.

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% for all three parameters, so the baseline is 3. The description does not add parameter-level details beyond what the schema provides—it repeats the 'max 9' constraint, which is already included in the destinations parameter description.

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 verb 'calculate' and the resource 'drive times from an origin to multiple campgrounds', and it specifies the method ('Mapbox routing with live traffic'). This distinguishes it from sibling tools like get_weather or check_availability, which address different concerns.

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 context for when to use the tool (when drive times to campgrounds are needed) and includes a key constraint ('Maximum 9 destinations per request'). However, it does not explicitly compare to alternatives or state when not to use it, so it lacks explicit exclusions.

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

All outdoorithm 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

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (search, details, availability, weather, etc.), but build_packing_list and get_gear_for_campground both deal with gear recommendations, and check_safety overlaps with the safety section in get_campground_details. However, the descriptions are detailed enough for an agent to choose correctly.

Naming Consistency4/5

Tool names follow a consistent verb_noun pattern (build_, calculate_, check_, compare_, find_, get_, prepare_, search_) with the exception of health_check, which reverses the order and breaks the pattern. This is a minor deviation.

Tool Count5/5

13 tools is well-scoped for a comprehensive outdoor trip planning server, covering search, details, availability, weather, safety, gear, and reservations without being excessive or sparse.

Completeness5/5

The server provides end-to-end coverage for planning a camping trip: search and filter campgrounds, get rich details, check availability, prepare reservations, evaluate safety, weather, drive times, gear recommendations, and packing lists. The only missing capability (direct booking) is intentionally excluded due to operator restrictions.

Resources