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

uber_get_auth_url

Generate an Uber authorization URL for user authentication to enable AI assistants to book and manage rides through the MCP Uber Server.

Instructions

Get the Uber authorization URL for user to authenticate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesUnique identifier for the user

Implementation Reference

  • Handler for uber_get_auth_url tool: parses userId from arguments, generates authorization URL using UberClient, and returns a text response with the URL.
    case 'uber_get_auth_url': {
      const { userId } = AuthorizeSchema.parse(args);
      const authUrl = await uberClient.getAuthorizationUrl(userId);
      return {
        content: [
          {
            type: 'text',
            text: `Please visit this URL to authorize Uber access: ${authUrl}`,
          },
        ],
      };
    }
  • Zod schema for input validation of uber_get_auth_url tool, defining the required userId parameter.
    const AuthorizeSchema = z.object({
      userId: z.string().describe('Unique identifier for the user'),
    });
  • src/index.ts:108-112 (registration)
    Registration of the uber_get_auth_url tool in the TOOLS array, including name, description, and input schema.
    {
      name: 'uber_get_auth_url',
      description: 'Get the Uber authorization URL for user to authenticate',
      inputSchema: zodToJsonSchema(AuthorizeSchema),
    },
  • UberClient method that constructs the Uber OAuth authorization URL using configuration parameters.
    async getAuthorizationUrl(state: string): Promise<string> {
      const params = new URLSearchParams({
        client_id: this.config.clientId,
        response_type: 'code',
        redirect_uri: this.config.redirectUri,
        scope: 'profile request ride_request',
        state,
      });
      return `${this.config.authBaseUrl}/oauth/v2/authorize?${params.toString()}`;
    }
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 an authorization URL but doesn't describe what the URL is used for, whether it's one-time use, expiration behavior, required user interaction, or error handling. For an authentication tool with zero annotation coverage, this is a significant gap.

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 with zero waste. It is appropriately sized and front-loaded, making it easy 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 authentication flows, no annotations, and no output schema, the description is incomplete. It doesn't explain what the authorization URL is, how it should be used, what the expected output format is, or potential errors. For a tool with critical security implications, this leaves significant gaps.

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 schema description coverage is 100%, with the single parameter 'userId' documented as 'Unique identifier for the user'. The description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 is appropriate given the schema does the heavy lifting.

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 ('Uber authorization URL'), and specifies the target ('for user to authenticate'). It distinguishes itself from siblings like ride management tools, though it doesn't explicitly differentiate from potential authentication-related siblings (none exist in the list).

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

Usage Guidelines3/5

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

The description implies usage in authentication flows but provides no explicit guidance on when to use this tool versus alternatives (e.g., uber_set_access_token for token management) or prerequisites. It suggests a context of user authentication but lacks details on timing or integration steps.

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