BinaSmart

Homes, land and shops for sale or rent in Addis Ababa

search_properties

Read-only

Live listings on bina.et/property from Addis Ababa real-estate companies' own websites, checked every week: title, price as the company wrote it (some per m² or in USD), bedrooms, size, area, the listing company with its own phone and WhatsApp, the date the company last updated it, and a bina.et link with every photo. Use for "apartment for rent in Bole", "3 bedroom for sale", "ቤት ኪራይ". Every listing and price is as the company published it.

Input Schema

Name	Required	Description
`area`	No	Neighbourhood in English or Amharic, e.g. Bole, Sarbet, CMC, Ayat, ሳርቤት
`beds`	No	At least this many bedrooms (0 = studio)
`type`	No	Property type
`limit`	No	Max results, default 5
`query`	No	Other words: a building, project or company name
`listing`	No	Buy (sale) or rent
`max_price`	No	Highest price in birr (total for sale, per month for rent)

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026

addedInput schema / properties / type / description
```
Added value: +"Property type"
```

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": {
+              "area": {
+                "description": "Area",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "company": {
+                "description": "Listing company",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "link": {
+                "description": "bina.et listing",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "listing": {
+                "description": "sale or rent",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "phone": {
+                "description": "Company phone",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "price": {
+                "description": "Price as the company wrote it",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "title": {
+                "description": "Title",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "type": {
+                "description": "Property type",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Listings from the companies' own websites"
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 28, 2026

TDQS

A3.8/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, and the description adds meaningful context beyond that: data is refreshed weekly, prices are unmodified (some expressed per m² or in USD), and listings carry the company's own phone/WhatsApp. The warning that prices are as-published rather than normalized is a genuinely useful behavioral caveat.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence front-loads the source and refresh cadence well, but it then spends most of its length enumerating returned fields even though an output schema exists, making that portion largely redundant. The three-sentence structure is legible but the field list could be trimmed without loss.

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 values need not be explained, and the annotations cover the safety profile. The description fills the remaining gaps an agent needs: provenance, refresh cadence, price-format caveats, and concrete query examples. The lack of any exclusion or alternative-tool guidance is the only notable gap.

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 the baseline is 3. The description adds the important note that prices may be written per m² or in USD, which bears on interpreting max_price (documented as birr), but it does not explain how to use area, beds, type, or limit beyond what the schema already states.

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 clearly identifies the resource (live Addis Ababa property listings sourced from real-estate companies' own sites via bina.et) and enumerates what each listing contains. There is no direct property sibling among the other search_* tools to differentiate from, so explicit sibling routing is absent, but the domain is unambiguous.

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 provides concrete example intents: "apartment for rent in Bole", "3 bedroom for sale", and the Amharic "ቤት ኪራይ", which tells the agent the kinds of queries this tool serves. It does not state when NOT to use it or name alternatives, so it stops short of explicit when/when-not guidance.

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.