Skip to main content
Glama

UpGrowth: business data for Algeria, Tunisia and Morocco

Search ANAE auto-entrepreneur activities

search_anae_activities
Read-only

Search the list of activities open to the auto-entrepreneur status in Algeria, as the platform of the Agence Nationale de l'Auto-Entrepreneur (ANAE) publishes it, grouped in domains. The list is fixed by an order of the minister in charge of start-ups (executive decree 23-197, art. 8) whose list is attached to the original and not printed in the Journal officiel: this answer is not a Journal officiel text and may lag its latest update (meta.activity_list says so). Liberal professions, regulated professions and activities, and crafts are excluded from the list (law 22-23, art. 2). Use it to check whether an activity can be practised as an auto-entrepreneur and to find its six-digit code. Returns a page of activities with code, labels and domain. meta.total is the number of matches. In Algeria an activity that has a regime of its own, today 080101 (micro-importation), also carries the object regime: read it before answering about that activity, it is not the ordinary auto-entrepreneur regime (see get_anae_activity). For Morocco (country MA) the status rests on two texts: decree 2-15-263 lists the excluded professions and decree 2-15-303 (Bulletin officiel no. 6432 of 21 January 2016, pages 60 and 61) sets lists 1 and 2 of the eligible activities, which its article 2 lets an order amend. This tool returns the professions that decree 2-15-263 excludes from the auto-entrepreneur status (architects, lawyers, doctors, notaries and so on), each with key (an UpGrowth identifier, code is null: Morocco gives them no code), status excluded and its legal basis. Lists 1 and 2 of decree 2-15-303 are not transcribed yet (to verify): a profession that is not in the answer is not thereby eligible, so never tell a user it is eligible or not eligible from this answer alone. Morocco needs an API key. Without an API key at most 10 rows come back and meta.truncated says when more matched, so do not present such a list as complete. For Tunisia (country TN) there is no list of activities: the one record is the regime of the auto-entrepreneur as the finance law 2023 states it (key regime), and meta.activity_list says that the official list of activities is not loaded, so an activity that is not in the answer is neither admitted nor excluded: never tell a user it is not eligible. Tunisia needs an API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_anae_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch text, at most 100 characters. Digits only: matches the ANAE codes that start with them. Words: every word must start a word of the activity label in French, Arabic or English. Accents and letter case are ignored. Leave it out to browse by domain.
langNoLanguage of the labels, notes and attribution text in the answer: fr (French, the default), ar (Arabic) or en (English).fr
limitNoMaximum number of results in the page, from 1 to 100. Defaults to 20. Without an API key at most 10 rows come back.
domainNoKeep only activities of this ANAE domain, given by its six-digit domain code (it ends in 0000), for example 010000 for Advice, Expertise and Training. Every result carries its domain. Not used for Tunisia (country TN): it has one regime record and no domains.
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.
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. Changed4 schema fields 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."
    • changedInput schema / properties / domain / description
      Previous value: -"Keep only activities of this ANAE domain, given by its six-digit domain code (it ends in 0000), for example 010000 for Advice, Expertise and Training. Every result carries its domain."New value: +"Keep only activities of this ANAE domain, given by its six-digit domain code (it ends in 0000), for example 010000 for Advice, Expertise and Training. Every result carries its domain. Not used for Tunisia (country TN): it has one regime record and no domains."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results in the page, from 1 to 100. Defaults to 20."New value: +"Maximum number of results in the page, from 1 to 100. Defaults to 20. Without an API key at most 10 rows come back."
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip, from 0 to 10000, to read the next pages. Defaults to 0. meta.total tells how many results match."New value: +"Number 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."
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a fixed, read-only list. Beyond the annotations it discloses substantial behaviour: without an API key only 10 rows return and meta.truncated flags incompleteness, paging is impossible without a key, Morocco and Tunisia return key_required, and meta.activity_list reports whether the official list is loaded or lagging. These are exactly the operational constraints an agent needs to answer safely.

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?

The first sentence front-loads the purpose well, but the body is a dense, unsegmented block of legal exposition, including citations like 'Bulletin officiel no. 6432 of 21 January 2016, pages 60 and 61' and article numbers that do not help an agent decide or invoke. The operational warnings (API key limits, don't infer eligibility) are valuable, but they are buried and mixed with statutory background, making the definition hard to scan.

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, and the description compensates by describing the return shape ('a page of activities with code, labels and domain') plus the meta fields total and truncated, and it explains the quite different return shapes for Morocco and Tunisia. Required warnings for a tool whose absence-of-result is legally ambiguous are present in full.

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 every parameter (q, lang, limit, domain, offset, country) is already documented with formats, ranges and defaults. The description only adds the cross-cutting rule that TN has no domains for the domain filter and that offset must be 0 without a key, which largely restates the schema. Baseline 3 applies since the schema carries the parameter burden.

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 opening sentence gives a specific verb and resource: searching the list of activities open to auto-entrepreneur status in Algeria, grouped by domain. It also distinguishes the tool from get_anae_activity, which it names as the place to read the regime object. However, the purpose is diluted by long country-specific paragraphs that describe materially different behaviour for MA (returns excluded professions, code is null) and TN (returns a single regime record), so an agent must reconstruct what the tool actually returns in the non-default cases.

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 states the concrete use case ('check whether an activity can be practised as an auto-entrepreneur and to find its six-digit code') and explicitly forbids concluding ineligibility from a missing result for Morocco and Tunisia. It routes the agent to get_anae_activity before answering about activities with their own regime such as 080101, and it spells out the API-key preconditions per country. Guidance on when to use and when not to conclude is explicit throughout.

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.