UberSync MCP Server

Select Ride

select_ride

Pick the preferred ride type from a fare estimate to move forward with booking. Specify the ride option to finalize your ride choice.

Instructions

Select one ride type from an estimate before booking it.

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": {
      "rideTypeId": "<rideTypeId>"
    },
    "name": "select_ride"
  }
}

Input Schema

Name	Required	Description	Default
`estimateId`	No
`rideTypeId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are present, so the description carries full behavioral burden. It reveals that selecting a ride type is a distinct step before booking, but does not disclose whether the selection persists, is reversible, or has side effects, nor any failure conditions. This is a significant gap for a state-changing action.

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, front-loaded sentence with no filler or repetition. Every word contributes to the core 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?

With no output schema and no annotations, the agent is left without information about return values, failure behavior, or prerequisites (e.g., a valid estimate that offers these ride types). The description covers only the high-level action.

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

Parameters1/5

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

Schema description coverage is 0% and the description provides no parameter meaning. estimateId and rideTypeId are not explained beyond the schema; the enum on rideTypeId helps, but the relationship between the parameters and the estimate is left implicit.

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 uses a specific verb ('Select') and a specific resource ('one ride type from an estimate'), with a clear temporal context ('before booking it'). This distinguishes it from sibling tools like book_ride and estimate_ride.

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?

The phrase 'before booking it' establishes a clear workflow position: the tool is used to choose a ride type from an estimate, prior to booking. It does not explicitly name alternatives or exclusions, but the context is sufficiently clear.

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