UberSync MCP Server

Get Driver Location

get_driver_location

Read-onlyIdempotent

Get the driver's current location and ride status for an active ride by providing the ride ID, so you can track progress and know exactly where the driver is.

Instructions

Get the current Uber driver location and ride status for an active 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_location"
  }
}

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.6/5.0

Behavior3/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior, and the description does not contradict these. It adds context that the tool returns both location and status for an active ride, but it does not disclose behavior for invalid or inactive ride IDs, or what the response format looks like.

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, concise sentence that front-loads the purpose and scope. Every word contributes to the agent's understanding, with no redundancy or filler.

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 simple one-parameter, read-only tool with comprehensive annotations, the description sufficiently conveys what the tool does and what it returns. The absence of output schema is mitigated by explicitly naming the output ('driver location and ride status'). Minor gaps around edge-case behavior are not critical for basic usage.

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 fully describes the sole parameter rideId, including its provenance ('returned by request_ride'), so the description does not need to add parameter details. The tool description adds no semantic information beyond the schema, which is acceptable given 100% schema coverage.

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 verb 'Get' and the resource 'current Uber driver location and ride status' for an active ride. It distinguishes itself from get_driver_details and get_ride_status by combining both pieces of information, though it does not explicitly call out any sibling tool.

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 an active ride' provides a contextual condition for use, but there is no explicit guidance on when to choose this over track_driver, get_ride_status, or get_driver_details. No alternatives or exclusions are mentioned, leaving the agent to infer the appropriate context.

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