Skip to main content
Glama
Ocean-Ch

google-maps-transit

by Ocean-Ch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_MAPS_API_KEYYesGoogle Maps API key, obtained from Google Cloud Console with Routes API and Places API (New) enabled.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_transit_commuteA

Returns commute routes between two addresses using real-time Google Maps data. Use this when the user asks about commute, travel time, or exact travel times between two addresses. Supports transit, driving, walking, bicycling, and two_wheeler modes. Supports multi-leg trips via the intermediates parameter (e.g. A→B→C). Returns up to 3 alternative routes, each with duration in minutes, transit lines used, number of transfers, and walking time.

search_placesA

Searches for places — restaurants, cafés, hotels, attractions, shops, parks, and more — using real-time Google Maps data.

        Use this when the user asks things like:
        • "Find coffee shops near the Eiffel Tower"
        • "Best sushi restaurants in downtown Seattle"
        • "Dog-friendly parks in Austin, TX"
        • "Museums open right now in London"
        • "Gas stations along Highway 1"

        Returns up to 20 results with name, address, star rating, price level, open/closed status, and type tags.
        To get phone number, website, opening hours, and user reviews for a specific result, pass its id to get_place_details.
get_place_detailsA

Returns detailed information about a specific place: phone number, website URL, full opening hours for each day of the week, a short editorial summary, and up to 5 user reviews.

        Always requires a place ID obtained from a prior search_places call.
        Use this as a follow-up when the user wants full details about one of the search results, e.g.
        • "What are the opening hours for that first restaurant?"
        • "Does it have a website I can check?"
        • "Show me the reviews for the top result."
compare_commutesA

Compares commute times from multiple candidate origins to a single shared destination using real-time Google Maps data.

        Perfect for questions like:
        • "Which of these 3 apartments has the best commute to my office?"
        • "I'm considering moving to Brooklyn, Queens, or Jersey City — which is fastest to Midtown?"
        • "Compare driving vs. transit isn't needed — just rank these addresses by commute time."

        Accepts 2–5 origin addresses. Returns them ranked fastest → slowest, each with the best
        available route (duration, distance, transit lines, traffic-aware driving time, etc.).
        Failed lookups for individual origins are surfaced as errors in-line rather than aborting the whole comparison.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation4/5

search_places and get_place_details are cleanly separated as search vs. detail lookup, and the commute tools have distinct scopes (point-to-point vs. multi-origin ranking). The only mild overlap is between get_transit_commute and compare_commutes, both of which compute routes, though the descriptions make the boundary fairly clear.

Naming Consistency5/5

All four tools follow a consistent snake_case verb_noun pattern: get_transit_commute, search_places, get_place_details, compare_commutes. The convention is predictable and self-explanatory.

Tool Count4/5

Four tools is slightly lean for a maps server covering both routing and place discovery, but each tool earns its place and there is no redundancy. It is well-scoped, just on the minimal side.

Completeness4/5

The surface covers commute/routing (including multi-leg and comparison ranking) and a full place search-plus-detail lifecycle. Minor gaps exist—no standalone distance matrix, geocoding, or turn-by-turn directions—but core agent workflows are supported.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources