BinaSmart

Quote a BinaSmart ride

quote_ride

Read-only

Fixed upfront price for a ride inside Addis Ababa, Ethiopia — no surge, cash or telebirr/Chapa. Returns distance, ETA and the fare for every vehicle tier (moto, bajaj, economy, comfort, XL). request_ride books at the fare this returns. Also returns book_url: a one-tap bina.et link with this route and fare for the user to confirm.

Input Schema

Name	Required	Description	Default
`pickup`	Yes	Pickup: a place name in Addis Ababa (e.g. "Edna Mall", "Bole Airport", "Piassa") or "lat,lng" like "9.0108,38.7578".
`dropoff`	Yes	Drop-off: a place name in Addis Ababa (e.g. "Edna Mall", "Bole Airport", "Piassa") or "lat,lng" like "9.0108,38.7578".

Output Schema

Name	Required	Description
`note`	No	How to use or present this result
`pickup`	No	Resolved pickup place
`quotes`	No	Fixed fare for each vehicle tier
`dropoff`	No	Resolved drop-off place
`eta_min`	No	Trip time in minutes
`book_url`	No	bina.et/ride link with this route for the user to confirm
`estimate`	No	true when the route time is an estimate
`source_url`	No	bina.et page this result comes from; cite it
`distance_km`	No	Route distance in km
`pickup_coords`	No	Pickup "lat,lng"
`dropoff_coords`	No	Drop-off "lat,lng"

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "book_url": {
+      "description": "bina.et/ride link with this route for the user to confirm",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "distance_km": {
+      "description": "Route distance in km",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "dropoff": {
+      "description": "Resolved drop-off place",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dropoff_coords": {
+      "description": "Drop-off \"lat,lng\"",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "estimate": {
+      "description": "true when the route time is an estimate",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "eta_min": {
+      "description": "Trip time in minutes",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "note": {
+      "description": "How to use or present this result",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pickup": {
+      "description": "Resolved pickup place",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pickup_coords": {
+      "description": "Pickup \"lat,lng\"",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "quotes": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "book_url": {
+                "description": "bina.et/ride link for this tier",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "eta_min": {
+                "description": "Driver arrival estimate in minutes",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "fare_etb": {
+                "description": "Fixed fare in birr",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "label": {
+                "description": "Tier name",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "label_am": {
+                "description": "Tier name in Amharic",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "seats": {
+                "description": "Seats",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "tier": {
+                "description": "Tier id to pass to request_ride",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Fixed fare for each vehicle tier"
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: no surge pricing, accepted payment methods (cash or telebirr/Chapa), the full tier list returned, and a book_url confirmation link. It stops short of stating auth requirements or rate limits.

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?

Three dense sentences with zero waste: the pricing promise and scope are front-loaded, the return contents follow, and the sibling routing closes. Every sentence carries distinct information.

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, so return values need not be enumerated, yet the description still names the key fields (distance, ETA, fare per tier, book_url) helpfully. Combined with annotations and a fully documented 2-param schema, nothing an agent needs 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 description coverage is 100% and both parameters are fully documented in the schema with format examples (place name or lat,lng). The description only reinforces the geographic constraint ('inside Addis Ababa'), adding little beyond the schema, so the baseline 3 applies.

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 (quote) and resource (ride), scopes it geographically (inside Addis Ababa, Ethiopia), and explicitly separates itself from the booking sibling: 'request_ride books at the fare this returns.' An agent can distinguish it from request_ride and get_ride_status without opening any 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?

The relationship to request_ride ('books at the fare this returns') makes the intended workflow clear: quote first, then book. It does not give explicit when-not conditions or name other alternatives, but the sequencing guidance is unambiguous.

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

All BinaSmart tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.