BinaSmart MCP Server

Ride status

get_ride_status

Read-only

Check a BinaSmart ride's status—dispatching, assigned, arriving, arrived, ontrip, completed, or cancelled—with driver, vehicle, and plate details once assigned via ride ID and booking phone.

Instructions

Current status of a BinaSmart ride (dispatching, assigned, arriving, arrived, ontrip, completed, cancelled) with driver name, vehicle and plate once assigned. Needs the ride id and the rider phone used to book.

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": {
      "ride_id": "<ride_id>",
      "rider_phone": "<rider_phone>"
    },
    "name": "get_ride_status"
  }
}

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.2/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds real value on top: the status state machine and the fact that driver name, vehicle and plate only appear 'once assigned'. It still says nothing about what happens on an unknown ride id or a phone mismatch.

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 sentences, front-loaded with the status enumeration and then the input requirement; there is no filler and nothing that could be cut without losing information.

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 description covers the status set and conditional driver/vehicle availability. It is nearly complete, with only edge-case behavior (invalid id, mismatched phone) left unstated.

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 100% and both parameters are already documented (ride_id returned by request_ride, Ethiopian phone formats). The description only restates that the ride id and booking phone are needed, adding no syntax or format detail beyond the schema. Baseline 3 is correct.

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

Purpose5/5

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

States a specific verb+resource ('Current status of a BinaSmart ride') and enumerates the full status lifecycle, which cleanly separates it from the sibling write operations request_ride, cancel_ride and quote_ride. An agent can route to it without opening the schema.

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?

It gives the precondition for a successful call ('Needs the ride id and the rider phone used to book'), which tells the agent this is a post-booking lookup rather than a booking action. It does not, however, explicitly name alternatives or state when not to use it.

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