UberSync MCP Server

Track Driver

track_driver

Track your ride in real time using the ride ID. Get driver coordinates, pickup, destination, progress, ETA, and current ride status.

Instructions

Return driver coordinates, pickup, destination, progress, ETA, and current ride status.

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": "track_driver"
  }
}

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?

No annotations are provided, so the description must carry the behavioral disclosure burden. It clearly implies a read-only operation ('Return') but does not disclose whether an active ride is required, whether data is real-time, or any error/edge-case behavior. Basic transparency is present, but richer context is missing.

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 a comma-separated list of returned fields. Every word contributes value, and there is no redundancy or fluff.

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?

Given the tool's low complexity (one parameter, no output schema), the description sufficiently covers the return payload by listing all key fields. It lacks any usage-context details, but those are partly captured in other dimensions; overall the picture is close to complete.

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 input schema describes rideId as 'Ride ID returned by request_ride', achieving 100% parameter coverage. The description adds no additional meaning about the parameter, so the schema already does the heavy lifting; baseline 3 is appropriate.

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 states a specific verb ('Return') and clearly enumerates the resource scope: driver coordinates, pickup, destination, progress, ETA, and current ride status. This distinguishes the tool from siblings like get_driver_location or get_ride_status by signaling a comprehensive tracking snapshot rather than a single-purpose lookup.

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 for tracking a driver mid-ride but never explicitly tells when to use this tool versus alternatives such as get_driver_location or get_ride_status. Given many ride-related siblings, explicit routing guidance would have been valuable; without it, the agent must infer the use case.

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