BinaSmart MCP Server

Licensed Ethiopian overseas employment agencies

list_overseas_agencies

Read-only

Find Ethiopian agencies approved to send domestic workers to GCC countries, with Ministry register status and per-country partner office details. Filter by UAE, KSA, Qatar, Kuwait, Bahrain, or Oman.

Instructions

Ethiopian agencies that send domestic workers to GCC countries, approved on BinaSmart/GCC Domestic: name, licence, whether it is in the Ministry of Labor and Skills register, and for each country its GCC partner office (the office families contact). Filter by country: UAE, KSA, Qatar, Kuwait, Bahrain, Oman. Recruitment is through LMIS only (Proclamation 1389/2025).

Input Schema

Name	Required	Description	Default
`country`	No	GCC destination country; omit for all

Output Schema

Name	Required	Description
`count`	No	Number of items returned
`updated`	No	When the list was last updated
`agencies`	No	Licensed agencies with their GCC partner offices
`source_url`	No	bina.et page this result comes from; cite it

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": {
+    "agencies": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Licensed agencies with their GCC partner offices"
+    },
+    "count": {
+      "description": "Number of items returned",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "updated": {
+      "description": "When the list was last updated",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv0.1.1Oct 18, 2026
- addedInput schema / properties / country / description
```
Added value: +"GCC destination country; omit for all"
```
First observedv0.1.0Oct 18, 2026

TDQS

A3.9/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 genuine context beyond them: the upstream source (BinaSmart/GCC Domestic), the Ministry of Labor and Skills register flag, and the note that recruitment runs through LMIS under Proclamation 1389/2025. It does not discuss pagination or result-set size, so not a 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?

Dense but front-loaded: the entity and returned fields come first, filtering second, legal context last. The explicit country enumeration partly duplicates the enum in the schema, which is the only real waste.

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 structure need not be explained, and the description still covers scope, filter behavior, data provenance, and a relevant legal constraint. Complete enough for an agent to call correctly, though result volume/ordering is unmentioned.

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?

The single parameter has 100% schema coverage including the enum and the 'omit for all' default, so the baseline is 3. The description only re-lists the same six country values, adding no syntax or semantic detail 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?

The description states a specific resource (Ethiopian overseas employment agencies licensed to send domestic workers to GCC countries) and the fields returned (name, licence, ministry-register status, per-country partner office). No sibling tool covers this domain, so it is unambiguous by construction.

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

Usage Guidelines3/5

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

It says how to narrow results by country and implies usage (looking up agencies/partner offices families contact), but never states when to call this versus other lookups or any preconditions. Usage is inferable rather than prescribed.

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