UberSync MCP Server

Get Driver Profile

get_driver_profile

Read-onlyIdempotent

Get assigned driver details for a ride by providing the driver ID from a ride or nearby-driver search. Fills the gap when standalone driver-profile lookup is not available.

Instructions

Get the assigned driver details for a ride. Standalone driver-profile lookup is not available in Uber’s Rider API.

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": {
      "driverId": "<driverId>"
    },
    "name": "get_driver_profile"
  }
}

Input Schema

Name	Required	Description	Default
`driverId`	Yes	Driver ID returned by a ride or nearby-driver search

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that this is ride-scoped and that standalone lookup is unsupported, which is useful context, but it does not describe return shape or additional behavioral constraints.

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?

Two short sentences, front-loaded with the core purpose and immediately followed by a key limitation. No filler or redundant content.

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-only lookup, the description is mostly complete: it tells the agent what the tool returns at a high level and warns about the standalone lookup limitation. There is no output schema, so one could ask for more return-field detail, but the description is adequate for correct invocation.

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 description coverage is 100%; the driverId parameter is documented as 'Driver ID returned by a ride or nearby-driver search.' The tool description adds little beyond that, so the schema carries the parameter semantics.

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 and resource: 'Get the assigned driver details for a ride.' It also distinguishes itself from standalone driver-profile lookup, clarifying that this is the ride-scoped path rather than a generic driver-profile endpoint.

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 description gives clear context: use this when you need the driver assigned to a specific ride. It also notes that standalone driver-profile lookup is not available in Uber's Rider API, which is a useful exclusion, though it does not explicitly name an alternative sibling tool.

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