UberSync MCP Server

Get Driver Details

get_driver_details

Retrieve a ride's assigned driver details, including rating, vehicle, registration, completed trips, and masked phone, using the ride ID.

Instructions

Get the assigned driver, rating, vehicle, registration, completed trips, and masked phone for a ride.

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": {
      "rideId": "<rideId>"
    },
    "name": "get_driver_details"
  }
}

Input Schema

Name	Required	Description	Default
`rideId`	Yes	Ride ID returned by request_ride

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It clearly indicates a read operation via 'Get' and lists returned fields, including the privacy-oriented 'masked phone.' It does not describe prerequisites, error behavior, or data availability conditions, but is adequate for a simple read tool.

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?

A single sentence that directly states the tool's purpose and returned fields with no redundant or filler content. The key scope ('for a ride') is clear and front-loaded.

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?

For a single-parameter read tool with no output schema, the description is mostly complete: it names the input context and enumerates the returned information. It could mention when driver info is available or that the phone is intentionally masked for privacy, but these are minor gaps for this simple tool.

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 coverage is 100%, and the rideId parameter is already described as 'Ride ID returned by request_ride.' The description adds no extra parameter detail, but none is needed given the schema's clarity.

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 names a specific verb (Get) and a specific resource (assigned driver, rating, vehicle, registration, completed trips, and masked phone for a ride). The field list makes it clearly distinguishable from siblings like get_driver_profile, get_ride_details, and get_driver_location.

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 phrase 'for a ride' implies this tool is used when an agent needs driver information tied to a specific ride. However, it gives no explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives such as get_driver_profile or get_ride_details.

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