BinaSmart

Licensed Ethiopian overseas employment agencies

list_overseas_agencies

Read-only

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
`note`	No	How to use or present this result
`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
`ministry_register`	No	The full Ministry of Labour and Skills register on bina.et, when no partner-checked agency is listed yet

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedOutput schema / properties / ministry_register

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The full Ministry of Labour and Skills register on bina.et, when no partner-checked agency is listed yet"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "How to use or present this result",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed2 schema fields changedOct 18, 2026

addedInput schema / properties / country / description

Added value: +"GCC destination country; omit for all"

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"
+}

AddedOct 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With readOnlyHint=true and openWorldHint=false already declaring the safety profile, the description usefully adds domain behavior: agencies are approved on BinaSmart/GCC Domestic, register status is part of the record, and recruitment is governed by LMIS under Proclamation 1389/2025. It does not cover auth needs or result completeness, but the added regulatory and data-provenance context is substantive.

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?

The description is front-loaded with what the tool returns and remains reasonably dense without filler. The final legal sentence adds context, though the long first sentence and repeated country enumeration make it slightly heavier than necessary.

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?

An output schema exists and annotations cover read-only safety, so the description need not explain return values or mutation risk. It still supplies useful domain context about register status and GCC partner offices; only pagination, ordering, and result completeness are left unaddressed.

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 the single country parameter is a fully enumerated, optional field whose schema description already says 'omit for all'. The description repeats the enum values but adds no syntax or filtering semantics beyond what the schema provides, so baseline 3 is appropriate.

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 gives a specific verb and resource: it lists Ethiopian overseas employment agencies sending domestic workers to GCC countries, and enumerates the returned fields (name, licence, register status, partner office). The purpose is unambiguous, but it does not explicitly differentiate itself from plausible siblings such as search_companies or get_employer.

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?

Usage is implied by the country filter and the domain context, so an agent can infer when to call it. However, there is no explicit when-to-use guidance, no named alternatives, and no statement of when this tool should not be used.

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.