UberSync MCP Server

Get Surge Status

get_surge_status

Read-onlyIdempotent

Check the current Uber demand multiplier at a pickup location to estimate fare increases before booking.

Instructions

Check the current Uber demand multiplier at a pickup location.

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_surge_status"
  }
}

Input Schema

Name	Required	Description	Default
`location`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds 'current' to indicate real-time data, but does not disclose output format, whether the multiplier is rounded/estimated, or any rate-limit or staleness behavior.

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 no filler. Every word contributes to the core meaning, making it easy to scan and quick for an agent to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup this is minimally sufficient: the agent knows what to query and what concept is returned. However, there is no output schema and the description does not say what the response looks like (e.g., a numeric multiplier, example values, or the meaning of 1.0), leaving some ambiguity for downstream handling.

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 nested schema documents address, latitude, and longitude well, but the top-level 'location' property has 0% schema description coverage. The description adds that this is a 'pickup location,' which helps disambiguate from destination, but it does not explain why all three subfields are required or how they interact.

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 specific operation: checking the current Uber demand multiplier at a pickup location. It is easy to distinguish from receipt/trip/payment tools, though it does not explicitly differentiate itself from nearby pricing tools like get_price_estimate.

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 'current... at a pickup location' implies the tool is for live surge checks at a pickup point, but there is no explicit guidance about when to prefer this over get_price_estimate, get_fare_breakdown, or get_ride_options. No exclusions or alternatives are mentioned.

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