BinaSmart

Cars for sale in Addis Ababa

search_cars

Read-only

Live new and used cars on bina.et/cars from Addis Ababa dealers' and car markets' own websites, checked every week: make, model, year, price, mileage, fuel, gearbox, the dealer with its own phone and WhatsApp, and a bina.et link with every photo. Use for "used Toyota", "SUV under 10 million birr", "electric car price", "BYD". Not for taxi rides. Source: the BinaSmart car listings at https://bina.et/cars.

Input Schema

Name	Required	Description
`body`	No	Body type
`fuel`	No	Fuel type
`make`	No	Brand, e.g. Toyota, Suzuki, BYD, Hyundai, Ford
`limit`	No	Max results, default 5
`model`	No	Model name, e.g. Corolla, Vitz, Dzire, Atto 3
`min_year`	No	Oldest model year to include, e.g. 2018
`condition`	No	New or used
`max_price`	No	Highest price in birr
`cheapest_first`	No	true to sort by lowest price first

Output Schema

Name	Required	Description
`note`	No	How to use or present this result
`count`	No	Number of items returned
`results`	No	Cars from the dealers' own websites
`source_url`	No	bina.et page this result comes from; cite it

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 18, 2026

addedInput schema / properties / body / description
```
Added value: +"Body type"
```
addedInput schema / properties / cheapest_first / description
```
Added value: +"true to sort by lowest price first"
```
addedInput schema / properties / condition / description
```
Added value: +"New or used"
```
addedInput schema / properties / fuel / description
```
Added value: +"Fuel type"
```

addedInput schema / properties / min_year / description

Added value: +"Oldest model year to include, e.g. 2018"

addedInput schema / properties / model / description

Added value: +"Model name, e.g. Corolla, Vitz, Dzire, Atto 3"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "description": "Number of items returned",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "note": {
+      "description": "How to use or present this result",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "results": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "condition": {
+                "description": "New or used",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "dealer": {
+                "description": "Dealer",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "fuel": {
+                "description": "Fuel",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "link": {
+                "description": "bina.et listing",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "make": {
+                "description": "Make",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "model": {
+                "description": "Model",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "phone": {
+                "description": "Dealer phone",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "price": {
+                "description": "Price as the dealer wrote it",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "title": {
+                "description": "Title",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Cars from the dealers' own websites"
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 28, 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 bar is lower, but the description still adds real context: weekly refresh cadence, provenance (dealers' own sites), and that results carry dealer phone/WhatsApp and a bina.et link with photos. It does not discuss pagination or the limit ceiling, so not a full 5.

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?

One dense, front-loaded passage that leads with the verb+resource before examples and exclusions. Minor waste: the bina.et URL appears twice, once inline and again as a trailing "Source:" line, which is redundant rather than clarifying.

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?

With an output schema present, return-value detail is not required, and the description covers purpose, freshness, provenance and routing. Given nine optional parameters and a curated dataset, it is complete enough to call correctly, though default behavior (limit=5) is left entirely to the schema.

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%, so all nine parameters are already documented with types, enums and bounds; baseline 3 applies. The description's example queries (price in birr, brand names, body types) loosely reinforce make/price/body fields but add no syntax or filtering semantics beyond the schema.

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 and resource (search live new/used cars) with a concrete scope: Addis Ababa dealers and car markets. The listed attributes (make, model, year, price, mileage, fuel, gearbox, dealer contact, photos) make it unmistakable against siblings like search_properties or search_hotels.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger examples ("used Toyota", "SUV under 10 million birr", "BYD") and an explicit exclusion ("Not for taxi rides"), which routes the agent toward quote_ride/request_ride. Both the when and the when-not are stated.

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.