UberSync MCP Server

Get Nearby Drivers

get_nearby_drivers

Read-onlyIdempotent

Retrieve real Uber ride availability and pickup ETAs for a given location. Use it to identify which ride categories you can book and estimated wait times.

Instructions

Get real Uber product availability and pickup ETAs near a location. Uber does not expose a list of nearby driver identities.

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": {
      "location": "<location>"
    },
    "name": "get_nearby_drivers"
  }
}

Input Schema

Name	Required	Description	Default
`category`	No
`location`	Yes
`radiusKm`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so safety is covered. The description adds meaningful behavioral context by explaining the tool returns product availability and ETAs rather than driver identities, which is important because the tool name is misleading.

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 two tight sentences with no filler. The primary purpose is front-loaded, and the clarifying limitation about driver identities earns its place by preventing a common misuse.

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 read-only query tool with nested location parameters and no output schema, the description conveys the essential return concept—product availability and pickup ETAs—and the key limitation. It does not explain category or radius semantics, but the schema provides enums and a default for those, so the description is nearly complete.

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

Parameters2/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-level guidance. The names and schema structures make 'location' and 'radiusKm' somewhat self-explanatory, and category is an enum, but the description does not compensate for the lack of schema descriptions as required when coverage is low.

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 real Uber product availability and pickup ETAs near a location.' It also corrects the potentially misleading tool name by noting that Uber does not expose nearby driver identities, clearly distinguishing this tool from driver-location or tracking siblings.

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 implies when to use the tool: when real product availability and pickup ETAs are needed near a location. It also states a clear when-not: it cannot list nearby driver identities. However, it does not explicitly name alternative sibling tools or provide routing conditions.

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