UberSync MCP Server

List Trips

list_trips

Read-onlyIdempotent

Retrieve recent completed or cancelled trips, with optional status filtering to review ride history.

Instructions

List recent completed or cancelled trips, optionally filtered by status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_trips"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds 'recent' and 'completed or cancelled' scoping but no additional behavioral traits like ordering, recency window, or pagination; there is no contradiction.

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?

A single front-loaded sentence with no filler. The core action and resource appear first, and the optional filter is appended clearly at the end.

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 list with rich annotations, the description covers the main purpose and the status parameter. However, the unresolved overlap with get_recent_rides and the lack of any mention of ordering or limit behavior keep it from being fully 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?

Schema description coverage is 0%, so the description carries extra weight. It adds meaning for status by naming 'completed or cancelled' and indicating the filter is optional, but it says nothing about the limit parameter beyond what the schema name/default/range already imply.

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?

States a specific verb ('List') and resource ('recent completed or cancelled trips'), with optional status filtering. However, it does not distinguish itself from sibling get_recent_rides, which may cover overlapping functionality.

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?

No guidance on when to use list_trips versus get_recent_rides or get_trip_details, and no exclusions or prerequisites are given. The optional status filter is the only usage hint, but it does not help an agent choose among overlapping siblings.

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