Skip to main content
Glama

Get ride status

get_ride_status
Read-onlyIdempotent

Get the live status of one of the verified phone's rides by its booking code. Requires session_token from verify_code. If the ride has a linked flight number, the response also reports whether a flight-delay-triggered reschedule has happened (Quo watches linked flights and proactively shifts the pickup time when one runs late), the returned when already reflects any such reschedule, no separate lookup needed.

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": {
      "session_token": "<session_token>",
      "code": "<code>"
    },
    "name": "get_ride_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesBooking confirmation code, from reserve_ride/reserve_and_pay's response or list_my_rides
session_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavior beyond that: it limits results to the verified phone's rides, explains that linked flights are watched and pickups proactively rescheduled, and clarifies that the returned `when` already reflects any reschedule so no separate lookup is needed. Error or not-found behavior is not covered, keeping it from a 5.

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 sentences, front-loaded with purpose and key, followed by the access requirement and the response nuance. The parenthetical about Quo's flight watching is informative rather than repetitive, so nothing feels wasted.

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 no output schema, the description carries return-value burden and does explain the notable field (`when` reflecting reschedules) and the flight-delay report. It is adequate for a simple two-parameter read tool, though the overall response shape for non-flight rides is only loosely implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% and the undocumented parameter is session_token; the description fills that gap by stating where it comes from (verify_code). It also reinforces `code` as a booking confirmation code tied to the verified phone, adding meaning beyond the schema's note.

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 ('Get the live status of ... rides'), plus the lookup key ('by its booking code') and the scope ('verified phone's'). An agent can distinguish this from list_my_rides, which enumerates rather than fetches a single ride by code.

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?

Explicitly states the prerequisite chain ('Requires session_token from verify_code'), which tells the agent it must verify before calling. It does not state when-not to use it or name list_my_rides as the alternative for browsing, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources