UberSync MCP Server

Share Trip

share_trip

Share a ride safely for demos by generating a representation that hides private contact information. Provide a ride ID to get a shareable trip view.

Instructions

Create a safe demo share representation without exposing private contact information.

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

Input Schema

Name	Required	Description	Default
`rideId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does state that private contact information is not exposed, which is a useful privacy guarantee, but it does not disclose whether this action mutates state, creates a persistent share link, requires authentication, or has other side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no filler and front-loads the primary action. It is compact and readable, though the phrasing 'safe demo share representation' is slightly awkward.

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

Completeness2/5

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

With no output schema and no annotations, the description should explain what the share representation looks like, how it is returned, and what the rideId is used for. It leaves all of these critical details unspecified, making it incomplete for reliable agent usage.

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?

The single parameter rideId is self-descriptive in the schema, but the description does not reference it at all. With schema description coverage at 0%, the description needed to explain how rideId is used or what the parameter represents, and it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action ('Create') and a resource ('safe demo share representation'), and the tool name confirms it relates to sharing a trip. However, 'safe demo share representation' is ambiguous about what is actually produced, and the description does not clearly distinguish this from related tools like get_trip_details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'safe demo' implies a demo/limited-use context, but there is no explicit guidance on when to use this tool versus alternatives. No sibling tools are referenced, and no exclusions or conditions are provided.

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