Skip to main content
Glama

UpGrowth: business data for Algeria, Tunisia and Morocco

by io.github.Z4KARY
OverviewDiscussionsAdmin

List wilayas and governorates

list_wilayas
Read-only

List the wilayas (provinces) of Algeria: 69 since loi n° 26-06 of 4 April 2026 (Journal officiel n° 25): the 58 numbered ones, then the 11 created by that law (Aflou, Barika, El Kantara, Bir El Ater, El Aricha, Ksar Chellala, Aïn Ouessara, Messaad, Ksar El Boukhari, Bou Saada, El Abiodh Sidi Cheikh), numbered 59 to 69 by décret présidentiel n° 26-206 of 25 May 2026 (Journal officiel n° 40), which come with their mother wilaya, their communes and in_place_by (their mother wilaya runs them until 31 December 2026 at the latest). For each wilaya in the dataset, with their two-digit code, their names in the three languages, capital, region and population, the address and phone of the local CNRC (trade register) office and the address of the local CASNOS (social security of the self-employed) office. Codes, names and capitals come from décret 84-79 (01 to 48), décret présidentiel 21-117 (49 to 58) and décret présidentiel 26-206 (59 to 69), cited in meta.sources; population, region, office details and websites do not come from the Journal officiel (meta.fields_not_from_jo). Use it to turn a wilaya code into a name or the reverse, or to find the local offices for a company registration or a CASNOS affiliation. For Tunisia (country TN) it lists the 24 governorates instead: code, ISO 3166-2 code, national statistics (INS) code, names in the three languages, chief town and the official source, and the answer names every page it was read on. For Morocco (country MA) it lists the 12 regions of the 2015 division the same way: code, ISO 3166-2 code, names in the three languages, chief town and the official source. The list is short and takes no filter. Tunisia and Morocco need an API key.

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the labels, notes and attribution text in the answer: fr (French, the default), ar (Arabic) or en (English).fr
countryNoCountry of the data, an ISO 3166-1 alpha-2 code in any letter case: DZ for Algeria, the default, TN for Tunisia or MA for Morocco. Only live countries answer: list_countries shows them and their datasets. Any other country, or a dataset the country does not have (for example the activity nomenclature for Morocco), returns country_not_available. Without an API key only DZ answers: TN and MA return key_required.DZ

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"Country of the data, an ISO 3166-1 alpha-2 code in any letter case: DZ for Algeria, the default, TN for Tunisia or MA for Morocco. Only live countries answer: list_countries shows them and their datasets. Any other country, or a dataset the country does not have, returns country_not_available."New value: +"Country of the data, an ISO 3166-1 alpha-2 code in any letter case: DZ for Algeria, the default, TN for Tunisia or MA for Morocco. Only live countries answer: list_countries shows them and their datasets. Any other country, or a dataset the country does not have (for example the activity nomenclature for Morocco), returns country_not_available. Without an API key only DZ answers: TN and MA return key_required."
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations it discloses key operational traits: 'Tunisia and Morocco need an API key,' and no-key behavior (TN/MA return key_required), plus the country_not_available failure mode. This is meaningful behavioral context an agent needs before calling.

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

Conciseness2/5

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

Purpose is front-loaded, but the body is a dense wall of legal provenance (loi n° 26-06, décret présidentiel 26-206, Journal officiel numbers, in_place_by deadlines) that does not help an agent select or invoke the tool. Much of it fails the 'every sentence earns its place' test.

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 no output schema, the description compensates thoroughly by enumerating the returned fields per country (code, ISO/INS codes, trilingual names, capital/chief town, region, population, CNRC/CASNOS office details). An agent knows what to expect back and which auth is required.

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 both lang and country are already documented in the schema. The prose largely restates country routing (DZ/TN/MA) and language choice rather than adding syntax or edge-case detail beyond it, so baseline 3 applies.

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 opening sentence names the specific resource and scope (wilayas/provinces of Algeria, plus TN governorates and MA regions) with a clear list verb. An agent can distinguish it from the singular get_wilaya and from list_communes/list_dairas without opening any schema.

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 gives concrete use cases: 'turn a wilaya code into a name or the reverse, or to find the local offices for a company registration or a CASNOS affiliation,' and states the list takes no filter. It does not explicitly name get_wilaya as the single-record alternative, so the when-not is only implied.

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

All UpGrowth: business data for Algeria, Tunisia and Morocco toolsInspect
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.

Resources