BinaSmart

Hospitals, clinics, dentists and doctors in Addis Ababa

search_health

Read-only

Find hospitals, clinics, dentists, laboratories, health centres and doctors in Addis Ababa from BinaSmart Health (bina.et/health, 250+ places from the city map plus services and doctors the facilities confirmed; doctors' licences are checked by the BinaSmart team). Filter by kind, sub-city, a place to be near (nearest first) and a specialty (children, gynecology, eye, heart, bone, fertility, skin, mental health, blood test). Returns each place's bina.et/health page, landline, sub-city, distance, and its services and doctors when known. Not medical advice; emergencies: 907.

Input Schema

Name	Required	Description
`area`	No	A sub-city: Bole, Kirkos, Arada, Yeka, Lideta, Gulele, Addis Ketema, Kolfe Keranio, Nifas Silk-Lafto, Akaki Kality, Lemi Kura (English or Amharic)
`kind`	No	lab = laboratory or diagnostic centre; doctor = individual doctors' profiles
`near`	No	A neighbourhood or landmark to be near, e.g. Piassa, CMC, Megenagna, Edna Mall. Nearest places first.
`limit`	No	Max results, default 6
`specialty`	No	A specialty, service or part of a name, e.g. children, gynecology, eye, blood test, Hayat

Output Schema

Name	Required	Description
`note`	No	How to use or present this result
`count`	No	Number of items returned
`results`	No	Hospitals, clinics, labs and doctors
`source_url`	No	bina.et page this result comes from; cite it

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": {
+    "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"
+                ]
+              },
+              "hours": {
+                "description": "Hours",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "kind": {
+                "description": "Type",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "name": {
+                "description": "Name",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "nameAm": {
+                "description": "Name in Amharic",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "phone": {
+                "description": "Phone",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "url": {
+                "description": "bina.et/health page",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Hospitals, clinics, labs and doctors"
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses data provenance and quality (250+ places from the city map, services and doctors confirmed by facilities, doctor licences verified by the BinaSmart team) plus the returned fields (bina.et page, landline, sub-city, distance). It also flags the non-clinical nature of the results and the emergency number, which annotations cannot convey.

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?

A single dense paragraph but well front-loaded: purpose, then filters, then returns, then disclaimer. Every clause carries information, though the filter/return/disclaimer run-ons in one block make it slightly harder to scan than it could be.

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?

With five optional parameters, an output schema, and read-only annotations already covering safety, the description supplies everything else an agent needs: filter semantics, result ordering, return shape, provenance and a scope disclaimer. Nothing material is left for the agent to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds meaning: the specialty list expands the enum-like value space (children, gynecology, eye, heart, bone, fertility, skin, mental health, blood test), and 'nearest first' documents the ordering semantics of the near parameter.

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?

Opens with a specific verb and resource (find hospitals, clinics, dentists, laboratories, health centres and doctors) scoped to Addis Ababa, and names the data source (BinaSmart Health, 250+ places). The health-only scope makes it unmistakable against siblings like search_places 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 Guidelines4/5

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

Enumerates the four usable filter dimensions (kind, sub-city, near, specialty) with concrete specialty examples, and sets a scope boundary ('Not medical advice; emergencies: 907'). It never explicitly states when to prefer a sibling such as search_places, so routing guidance is implicit rather than 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.