UberSync MCP Server

Choose Payment Method

choose_payment_method

Select a payment method, Cash or Demo Wallet, for the next demo ride. Provide the payment method ID to set how the trip will be paid.

Instructions

Choose Cash or Demo Wallet for the next demo ride.

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": {
      "paymentMethodId": "<paymentMethodId>"
    },
    "name": "choose_payment_method"
  }
}

Input Schema

Name	Required	Description	Default
`paymentMethodId`	Yes	Payment method ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says to 'Choose Cash or Demo Wallet' without describing side effects, whether this changes the default, whether any charge occurs, or whether the selection is temporary. It also does not mention permissions or reversibility, which is a meaningful gap for a mutation-like tool.

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 one short sentence with no filler. It front-loads the action and immediately conveys the core purpose and the valid choices. Every word earns its place.

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?

The tool is simple with one required parameter and no output schema, so a very detailed description is not necessary. However, it omits useful context such as how to obtain a valid paymentMethodId, whether to call get_payment_methods first, and what side effects the choice has. The description is adequate but has notable gaps.

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?

The input schema only says 'Payment method ID,' which is generic. The description adds useful semantic detail by indicating that the valid choices are Cash or Demo Wallet for a demo ride. It does not specify the exact string values for paymentMethodId, but it provides more meaning than the schema alone.

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 states a specific action ('Choose') and resource ('payment method') with a clear context: 'for the next demo ride.' It does not explicitly distinguish itself from sibling set_default_payment_method, but the 'next demo ride' wording strongly implies a ride-scoped selection rather than a default-setting operation.

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 'for the next demo ride' provides some usage context, implying the tool is used during demo ride setup. However, it does not explicitly say when to use this tool instead of alternatives like set_default_payment_method, get_payment_methods, or list_payment_methods. The guidance is implied rather than stated.

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