BinaSmart MCP Server

Cancel a ride

cancel_ride

DestructiveIdempotent

Cancel a booked BinaSmart ride before it starts using ride ID and rider phone; cancellation is final and cannot be undone.

Instructions

Cancels a BinaSmart ride that has not started yet. A cancellation cannot be undone. Needs the ride id and the rider phone used to book.

Input Schema

Name	Required	Description	Default
`ride_id`	Yes	Ride id returned by request_ride
`rider_phone`	Yes	Ethiopian phone number used to book the ride, e.g. 0911234567 or +251911234567

Output Schema

Name	Required	Description
`note`	No	How to use or present this result
`test`	No	true for a reviewer test booking (no driver is sent)
`tier`	No	Vehicle tier
`driver`	No	Assigned driver, null until one is assigned
`pickup`	No	Pickup place
`status`	No	dispatching, assigned, arriving, arrived, ontrip, completed, cancelled, or test_booking
`dropoff`	No	Drop-off place
`ride_id`	No	Ride id (needed for get_ride_status and cancel_ride)
`fare_etb`	No	Fixed fare in birr
`source_url`	No	bina.et page this result comes from; cite it
`requested_at`	No	When the ride was requested (ISO time)
`tracking_url`	No	Live tracking page
`payment_method`	No	cash, telebirr or chapa
`payment_status`	No	Payment status

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.2Oct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "driver": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "name": {
+              "description": "Driver name",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "phone": {
+              "description": "Driver phone",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "plate": {
+              "description": "Plate number",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "rating": {
+              "anyOf": [
+                {
+                  "type": [
+                    "number",
+                    "string"
+                  ]
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Driver rating"
+            },
+            "vehicle": {
+              "description": "Vehicle"
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Assigned driver, null until one is assigned"
+    },
+    "dropoff": {
+      "description": "Drop-off place",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fare_etb": {
+      "anyOf": [
+        {
+          "type": [
+            "number",
+            "string"
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Fixed fare in birr"
+    },
+    "note": {
+      "description": "How to use or present this result",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "payment_method": {
+      "description": "cash, telebirr or chapa",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "payment_status": {
+      "description": "Payment status",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pickup": {
+      "description": "Pickup place",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "requested_at": {
+      "description": "When the ride was requested (ISO time)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ride_id": {
+      "description": "Ride id (needed for get_ride_status and cancel_ride)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "dispatching, assigned, arriving, arrived, ontrip, completed, cancelled, or test_booking",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "test": {
+      "description": "true for a reviewer test booking (no driver is sent)",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "tier": {
+      "description": "Vehicle tier",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tracking_url": {
+      "description": "Live tracking page",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedv0.1.1Oct 18, 2026
- addedInput schema / properties / ride_id / description
```
Added value: +"Ride id returned by request_ride"
```
- addedInput schema / properties / rider_phone / description
```
Added value: +"Ethiopian phone number used to book the ride, e.g. 0911234567 or +251911234567"
```
First observedv0.1.0Oct 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is covered structurally. The description adds real context beyond them: the cancellation is irreversible and only valid pre-start. It does not disclose the effect on fares/refunds or that repeat calls are safe (idempotency), which the annotations already imply.

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?

Two tight sentences, front-loaded with the action and its precondition, then the irreversibility warning and the required inputs. No filler.

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

Completeness5/5

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

An output schema exists and annotations carry the safety profile, so the description need only convey action, precondition, and required inputs — all of which are present. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 100% — both ride_id and rider_phone are fully documented in the schema, including format examples. The description only restates that both are needed ('the ride id and the rider phone used to book'), adding no syntax or edge-case detail beyond the schema.

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 ('Cancels a BinaSmart ride') plus a scope constraint ('that has not started yet'), which separates it from request_ride/quote_ride/get_ride_status. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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?

Gives a clear applicability condition: use it only for a ride that has not started. It does not name what to do instead once a ride is underway or already cancelled, so no explicit alternatives or exclusions are provided.

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