Skip to main content
Glama
199-mcp
by 199-mcp

uber_get_ride_status

Check the current status of your Uber ride request to track driver location, estimated arrival time, and trip progress.

Instructions

Get the current status of a ride request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesUnique identifier for the user
requestIdYesRide request ID

Implementation Reference

  • Handler function for uber_get_ride_status tool: validates input, checks user token, calls uberClient.getRideStatus, and returns JSON response.
    case 'uber_get_ride_status': {
      const { userId, requestId } = RideStatusSchema.parse(args);
      
      const token = userTokens.get(userId);
      if (!token) {
        throw new Error('User not authenticated. Please authorize first.');
      }
      
      uberClient.setAccessToken(token);
      const status = await uberClient.getRideStatus(requestId);
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(status, null, 2),
          },
        ],
      };
    }
  • Zod schema for input validation of uber_get_ride_status tool (userId and requestId).
    const RideStatusSchema = z.object({
      userId: z.string().describe('Unique identifier for the user'),
      requestId: z.string().describe('Ride request ID'),
    });
  • src/index.ts:128-132 (registration)
    Tool registration in TOOLS array with name, description, and input schema.
    {
      name: 'uber_get_ride_status',
      description: 'Get the current status of a ride request',
      inputSchema: zodToJsonSchema(RideStatusSchema),
    },
  • Core implementation in UberClient: API call to Uber's /v1.2/requests/{requestId} endpoint.
    async getRideStatus(requestId: string): Promise<RideRequest> {
      const response = await this.api.get(`/v1.2/requests/${requestId}`);
      return response.data;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves status, implying a read-only operation, but doesn't cover critical aspects like authentication requirements, rate limits, error conditions, or what the status response includes (e.g., driver location, ETA). This leaves significant gaps for safe and effective use.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a ride status tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the status includes (e.g., pending, en route, completed), how to interpret results, or error handling, which are essential for an agent to use this tool effectively in real-world scenarios.

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?

The input schema has 100% description coverage, clearly documenting both required parameters ('userId' and 'requestId'). The description doesn't add any meaning beyond the schema, such as explaining how to obtain these IDs or their format, but the schema's completeness justifies the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('current status of a ride request'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'uber_get_auth_url' or 'uber_get_price_estimates', which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a ride request ID from 'uber_request_ride'), exclusions, or comparisons to siblings like 'uber_cancel_ride', leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/199-mcp/mcp-uber'

If you have feedback or need assistance with the MCP directory API, please join our Discord server