Skip to main content
Glama

UpGrowth: business data for Algeria, Tunisia and Morocco

Get an ANAE activity

get_anae_activity
Read-only

Get one activity of the Algerian ANAE nomenclature (auto-entrepreneur status) by its six-digit code, for example 010101: its labels in French, Arabic and English and its domain. Use it when the user gives a code, or after search_anae_activities. Returns an error when the code does not exist. In Algeria an activity that has a regime of its own carries the optional object regime, present only then and today only for 080101, micro-importation: note (the facts in French, Arabic and English: who may import, at most 1,800,000 DZD of goods per trip and two trips a month, the card and the general authorisation of the Ministry of Foreign Trade, the conditions, the advantages, the obligations, the exclusions), legal_reference (executive decree n° 25-170 of 28 June 2025, JO n° 40 of 2025, and the finance law for 2026, law no. 25-17, JO n° 88 of 2025, art. 143, which sets the 5 % customs duty, the exemptions and the flat single tax of 0.5 % per import) and source_url (the Journal Officiel PDF of the decree). That activity is NOT governed by the ordinary auto-entrepreneur limits (finance law 2026, art. 143: micro-importers are eligible notwithstanding the legislation in force, and no text read sets a yearly ceiling of its own for them): never present the 5 million DZD yearly turnover ceiling of the ordinary status as its limit, and read regime.note before answering about it. For Tunisia (country TN) pass the key regime: you get who qualifies (Tunisian nationality, individual practice, the sectors, the ceiling of 75,000 dinars of yearly turnover), the exclusions, the duration, the registration, the single contribution with what it replaces and what it is made of, the late payment fine and the deregistration, each with the article of the law it comes from. The official list of activities is not loaded: say so, and never present the absence of an activity as an exclusion. For Morocco (country MA) pass the key of an excluded profession (for example avocats) to get it with the regime, or the key regime to get the regime alone: the definition, the turnover ceilings (500 000 and 200 000 dirhams), the tax rates (0.5 % and 1 %), the obligations and the legal texts (law 114-13 and its decrees).

Input Schema

NameRequiredDescriptionDefault
codeYesANAE activity code, six digits, for example 010101. For Morocco (country MA) it is the key of an excluded profession, for example avocats, or regime. Find codes with search_anae_activities. For Tunisia (country TN) it is the key of the regime record: regime (statut and ae are accepted too); Tunisia has no activity codes.
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. Changed3 schema fields changed
    • changedInput schema / properties / code / description
      Previous value: -"ANAE activity code, six digits, for example 010101. Find codes with search_anae_activities."New value: +"ANAE activity code, six digits, for example 010101. For Morocco (country MA) it is the key of an excluded profession, for example avocats, or regime. Find codes with search_anae_activities. For Tunisia (country TN) it is the key of the regime record: regime (statut and ae are accepted too); Tunisia has no activity codes."
    • changedInput schema / properties / code / pattern
      Previous value: -"^[0-9]{6}$"New value: +"^([0-9]{6}|[A-Za-z0-9][A-Za-z0-9_-]{1,99})$"
    • 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.5/5.0
Behavior5/5

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

Beyond the readOnly annotation, it discloses error behavior for non-existent codes, country availability rules (only live countries answer; without an API key only DZ answers), and key_required/country_not_available outcomes. It also warns against misapplying the ordinary 5 million DZD ceiling to micro-importation and directs the reader to regime.note, adding substantial behavioral context.

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 in the first sentence, but the remainder is a very dense, parenthetical block mixing Algerian, Tunisian, and Moroccan rules. While most details are potentially useful, the description is far longer than needed and would benefit from tighter grouping and shorter sentences.

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 and three parameters, the description does the heavy lifting by describing what is returned (labels, domain, optional regime object), error cases, country-specific behavior, and legal caveats. It is complete enough for an agent to invoke and interpret the tool correctly across all supported countries.

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 coverage is 100%, so the structured parameter descriptions already carry the detailed semantics for code, lang, and country. The description mostly repeats the schema's code examples and adds no parameter-level detail beyond what is already there, 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?

The first sentence states the exact verb and resource: get one ANAE activity by six-digit code, returning labels in French, Arabic, and English. It clearly distinguishes this from search_anae_activities and explains its broader country-specific uses for TN and MA, so an agent can identify the tool without ambiguity.

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

Usage Guidelines5/5

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

It explicitly says to use it when the user gives a code or after search_anae_activities, and gives precise conditions for Tunisia (pass the key regime) and Morocco (pass a profession key or regime). It also warns about cases where the official list is not loaded and about not treating absence as exclusion, covering when-not-to-use implications.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.