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

uber_cancel_ride

Cancel an ongoing Uber ride request by providing user and request IDs to manage ride bookings.

Instructions

Cancel an ongoing ride request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesUnique identifier for the user
requestIdYesRide request ID to cancel

Implementation Reference

  • Handler for the uber_cancel_ride tool: parses arguments using CancelRideSchema, retrieves and sets user access token, calls uberClient.cancelRide(requestId), and returns a success message.
    case 'uber_cancel_ride': {
      const { userId, requestId } = CancelRideSchema.parse(args);
      
      const token = userTokens.get(userId);
      if (!token) {
        throw new Error('User not authenticated. Please authorize first.');
      }
      
      uberClient.setAccessToken(token);
      await uberClient.cancelRide(requestId);
      
      return {
        content: [
          {
            type: 'text',
            text: 'Ride cancelled successfully',
          },
        ],
      };
    }
  • Zod input schema definition for the uber_cancel_ride tool, specifying userId and requestId parameters.
    const CancelRideSchema = z.object({
      userId: z.string().describe('Unique identifier for the user'),
      requestId: z.string().describe('Ride request ID to cancel'),
    });
  • src/index.ts:133-137 (registration)
    Registration of the uber_cancel_ride tool in the TOOLS array, including name, description, and input schema.
    {
      name: 'uber_cancel_ride',
      description: 'Cancel an ongoing ride request',
      inputSchema: zodToJsonSchema(CancelRideSchema),
    },
  • Core helper method in UberClient that performs the HTTP DELETE request to the Uber API to cancel a ride by requestId.
    async cancelRide(requestId: string): Promise<void> {
      await this.api.delete(`/v1.2/requests/${requestId}`);
    }
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 action ('Cancel') but lacks details on side effects (e.g., cancellation fees, refund policies), permissions required, rate limits, or error conditions. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero waste. It is front-loaded with the core action and resource, making it easy to parse. Every word earns its place by directly contributing to understanding the tool's purpose.

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 tool's complexity as a mutation operation with no annotations and no output schema, the description is incomplete. It fails to address critical aspects like return values, error handling, or behavioral implications (e.g., irreversible changes). This leaves significant gaps for an AI agent to use the tool effectively.

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%, with both parameters ('userId' and 'requestId') documented in the schema. The description does not add any parameter-specific details beyond what the schema provides, such as format examples or contextual usage. The baseline score of 3 reflects adequate but minimal value addition.

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 specific action ('Cancel') and resource ('an ongoing ride request'), distinguishing it from sibling tools like 'uber_request_ride' (create) or 'uber_get_ride_status' (read). It uses precise language that directly communicates the tool's function without ambiguity.

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 does not mention prerequisites (e.g., needing an active ride request), exclusions (e.g., cannot cancel completed rides), or comparisons with sibling tools like 'uber_get_ride_status' for checking status first. Usage is implied but not explicitly defined.

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