Skip to main content
Glama
Sign In
uber-mcp

uber-mcp

by benjamin-di
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cancel a reservation

uber_cancel_reservation
Destructive

Cancel a future Uber reservation by previewing the cancellation fee without confirm, then approve using the same reservation ID and token.

Instructions

Cancel a specific future reservation. Without confirm: preview the reservation and current cancellation fee. After approval: same id and confirm token. Changed terms require a new preview; cancellation remains available while booking is frozen. Never retry an unknown outcome without checking Uber.

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": {
      "id": "<id>"
    },
    "name": "uber_cancel_reservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description adds material context beyond them: the call is two-stage with a fee preview, the confirm token is reused with the same id, changed terms invalidate a preview, and unknown outcomes must not be retried blindly. That last warning is genuine complementary guidance for a non-idempotent destructive operation.

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?

Purpose is front-loaded in the first sentence, and every following sentence addresses a distinct operational concern with no filler. The phrasing is dense to the point of telegraphic ('After approval: same id and confirm token'), which costs a little readability.

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?

An output schema exists, so return values need no explanation, and the destructive two-parameter surface is well covered: fee preview, token reuse, frozen-booking edge case, retry safety. It does not state whether a completed cancellation can be undone or restored, the one notable gap for a destructive tool.

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

Parameters4/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 the burden, and it does explain that 'confirm' is an approval token paired with the same 'id' from the preview step. It does not disclose the id's format or length constraints (a 36-character UUID), which remain inferable only from the raw schema types.

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 and resource with scope: 'Cancel a specific future reservation.' The word 'future' implicitly separates it from uber_cancel_ride for active rides, but it never names that sibling explicitly, so differentiation requires inference.

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 explains the two-phase usage pattern clearly: call without confirm to preview and see the fee, call with confirm after approval. It also notes that changed terms require a fresh preview and that cancellation is still possible while a booking is frozen, giving concrete conditions for each call. It stops short of naming when to prefer uber_cancel_ride instead.

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

Deploy Server

Other Tools