Skip to main content
Glama

Get travel time

well_get_travel_time
Read-only

Get how long one trip takes and how far it is, from Google Maps: "the drive to the 10:00 meeting", "le trajet jusqu'au match de samedi". Call it once per event that has a location when the person asks for the travel time. Pass destination: the event's location copied as the event or the mail states it. Pass origin only when the person has an event with a location just before it that day (give that location) or when the person gave a start address; otherwise leave it out and the trip starts from the workspace's own address. Leave mode out for a car trip unless the person named another way. Pass departure_at when the time the person leaves is known, so a car trip reads traffic. An event with no location gets no call: say its travel time is unknown. The tool runs at most 12 times per turn.

Returns status "found" with duration_minutes, distance_km, mode, origin_kind and origin, or "no_route" when Google Maps found no route. Give the duration as the tool returns it, say it comes from Google Maps, and when origin_kind is "workspace_address" say the trip starts from the workspace's address. Never estimate, compute or recall a travel time or a distance the tool did not return. On a failure, error_reason is one of "origin_required" (no start was given and the workspace has no address on file: ask the person where they leave from), "call_limit_reached" (this turn already asked enough trips), "daily_limit_reached" (the person or the workspace reached today's limit) or "travel_time_unavailable" (the travel time cannot be read now). Then say in the person's language that the travel time is not available and why, and give no figure.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoHow the person travels. Leave it out for "car" unless the person named another way.
originNoWhere the trip starts, only when it is known: the location of the person's previous event that day, or an address the person gave. Leave it out to start from the workspace's own address.
destinationYesWhere the trip ends: the location of the event as the event or the mail states it, or an address the person gave. Copy it; never invent or complete an address.
departure_atNoWhen the person leaves, ISO 8601 with an offset. A car trip then reads traffic at that time.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
originNo
sourceNo
statusNo
successYes
distance_kmNo
origin_kindNo
error_reasonNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
duration_minutesNo
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / newly_connected / description
      Previous value: -"Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. Start the reply with one line per entry, in the person's language: \"<name> is connected.\". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later."New value: +"Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: \"<name> is connected.\". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later."
  2. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources