Skip to main content
Glama

UpGrowth: business data for Algeria, Tunisia and Morocco

by io.github.Z4KARY
OverviewDiscussionsAdmin

List the communes of Algeria with their postal codes

list_communes
Read-only

List the communes (baladiyas) of Algeria from Algérie Poste's official data, read every day: each with its four-digit commune code, its French and Arabic names, its wilaya (number and names), its wilaya under loi n° 26-06 of 2026 when it is one of the 108 communes of the 11 wilayas that law created (wilaya_2026: its number 59 to 69 and slug), its postal codes and how many post offices and ATMs it has, and its daïra (daira: name, kind, wilaya; décret exécutif n° 91-306 as amended, Algiers' circonscriptions administratives). Filter by daira, by wilaya (a number from 1 to 69, 59 to 69 being the wilayas of 2026, or their slug such as aflou, barika, bou-saada) and by q (a name in French or Arabic, accents ignored, or the start of a postal code). Use it to check that a commune exists, to find its postal codes, or to list the communes a delivery zone covers. Algérie Poste lists 1,540 communes (those with a post office); the law counts 1,541. Without an API key, at most 10 rows. Algeria only.

Input Schema

NameRequiredDescriptionDefault
qNoA commune name in French or Arabic (accents ignored), or the first digits of a postal code.
langNoLanguage of the labels, notes and attribution text in the answer: fr (French, the default), ar (Arabic) or en (English).fr
dairaNoOnly the communes of this daïra (or Algiers circonscription administrative), by name, accents ignored.
limitNoMaximum number of results in the page, from 1 to 100. Defaults to 20. Without an API key at most 10 rows come back.
offsetNoNumber of results to skip, from 0 to 10000, to read the next pages. Defaults to 0. meta.total tells how many results match. Without an API key it must be 0: a search cannot be paged.
wilayaNoA wilaya number from 1 to 69 (16 for Alger, 59 to 69 the wilayas of 2026), or the slug of a wilaya created in 2026 (aflou, barika, el-kantara, bir-el-ater, el-aricha, ksar-chellala, ain-ouessara, messaad, ksar-el-boukhari, bou-saada, el-abiodh-sidi-cheikh).
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
    • addedInput schema / properties / daira
      Added value: +{
+  "description": "Only the communes of this daïra (or Algiers circonscription administrative), by name, accents ignored.",
+  "maxLength": 60,
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the operational burden and does so well: no-API-key truncation to 10 rows, offset must be 0 without a key (no paging), only DZ answers unauthenticated while TN/MA return key_required, non-covered datasets return country_not_available, and the data is refreshed daily. It also discloses the 1,540-vs-1,541 count discrepancy between the source and the law.

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 purpose is front-loaded, but the core sentence is a single run-on enumeration of every returned field, and domain trivia such as 'décret exécutif n° 91-306' does not help an agent select or invoke the tool. It is information-dense rather than concise, and harder to scan than it needs to 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?

There is no output schema, so the description must describe the return shape itself, and it enumerates every field (commune code, FR/AR names, wilaya, wilaya_2026, postal codes, post-office/ATM counts, daïra). Combined with filter semantics and the API-key/pagination caveats, an agent has everything needed for a 7-parameter, zero-required tool.

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 coverage is 100%, so baseline is 3, but the description adds real meaning: it ties wilaya numbers 59–69 to loi n° 26-06 and lists the 2026 slugs, explains that q ignores accents and accepts a postal-code prefix, and clarifies daïra includes Algiers' circonscriptions administratives. Some of this duplicates the schema, keeping it below a 5.

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?

States a specific verb (List) and resource (communes/baladiyas of Algeria) and enumerates the fields returned, including the 2026-wilaya and daïra dimensions. An agent can tell this apart from get_commune (single lookup), list_wilayas and 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?

Explicitly names three use cases: checking a commune exists, finding postal codes, and listing the communes a delivery zone covers, plus which filters to combine (daira, wilaya, q). It lacks an explicit contrast with the sibling get_commune for the single-record case, so it stops short of full when-to-use/when-not coverage.

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