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 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. 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.

Input Schema

TableJSON 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, returns country_not_available.DZ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true), and the description adds substantial behavioral context: exactly which fields are returned per country, that it is short/unfiltered, and that the answer names every source page. It does not mention error behavior in prose (that lives in the schema).

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?

Front-loads the primary (Algeria) behavior and its use cases before the country variants. The TN and MA field lists are near-verbatim repeats and could be compressed, so not a 5.

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 carries the return-shape burden and does so per country, including codes, names, offices and attribution. Nothing an agent needs to call it correctly is missing.

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 fully documented with defaults, enum and pattern. The description adds no format or syntax detail beyond the schema, so the baseline of 3 is appropriate.

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 and resource ('List the wilayas of Algeria'), and precisely varies scope by country (TN governorates, MA regions). An agent can distinguish it from the singular sibling get_wilaya from the text alone.

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?

Gives concrete use cases ('turn a wilaya code into a name or the reverse', 'find the local offices for a company registration or a CASNOS affiliation') and notes it takes no filter. No explicit alternative named (e.g. get_wilaya for a single record), so it stops short of a 5.

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