Skip to main content
Glama

UpGrowth: business data for Algeria, Tunisia and Morocco

Get the tax and social filing calendar of Algeria

get_tax_calendar
Read-only

Get the legal filing and payment deadlines of businesses in Algeria, each with who must file, the deadline as the text words it, its article and the official text it was read in (the 2026 tax codes of the Directorate General of Taxes, checked on 20 October 2026 against the finance laws of the Journal officiel, and the CNAS and CASNOS sites): the monthly VAT return and payment (G50, within the first 20 days of each month, CTCA art. 76-1, and every quarter under the simplified regime, art. 78 bis), the withholding tax on salaries, pensions and annuities (by the 20th, monthly or quarterly, CIDTA art. 129-1), the IBS advance payments (20 March, 20 June and 20 November, art. 356) and the IRG advance payments (art. 355), the IFU forecast return G12 and the IFU minimum (by 30 June), the IFU payment in full or in instalments (50 %, then 1-15 September and 1-15 December), the IFU final return G12 bis (by 20 January of the next year), the IFU option for the real regime (before 1 February) and the IFU late filing increases (10 %, 20 %, 25 %), the declaration of existence (within 30 days of the start of the activity), the annual profit return (by 30 April), the annual summary statement ERA (before 30 September), the annual IRG return (by 30 June), the special return of the IRG result (by 30 April), the transfer pricing return (by 30 April), the vocational training and apprenticeship taxes (every half year, by the 20th of the following month), the penalty for an annual return not filed (25 %, reduced to 10 % or 20 % when filed within two months, 35 % after a formal notice), the CNAS contributions (within 30 days of each quarter or month), the CNAS annual declaration DAS (within 30 days of the year end) and affiliation (within 10 days of hiring), and the CASNOS base declaration (by 1 March) and annual contribution (before 1 July, before 1 October for people carrying on an agricultural activity only). A deadline on a legal holiday moves to the next working day. The list is not exhaustive: other taxes and returns of the codes are not included, and the extensions of deadlines decided by the DGI (law 23-15, art. 14) are not listed. Filters: q (words, accents ignored, e.g. "IFU" or "CNAS") and treatment (monthly, quarterly, semiannual, annual, advance, ifu, social, penalty, general). Algeria only (country DZ); other countries return country_not_available.

Input Schema

NameRequiredDescriptionDefault
qNoWords that must all appear in the item (label, who, deadline, legal basis), accents and case ignored, for example G50, IFU, CNAS, 30 avril.
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
treatmentNoOnly the obligations of this kind.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / treatment / enum
      Previous value: -[
      -  "monthly",
      -  "quarterly",
      -  "annual",
      -  "ifu",
      -  "social",
      -  "penalty",
      -  "general"
      -]New value: +[
      +  "monthly",
      +  "quarterly",
      +  "semiannual",
      +  "annual",
      +  "advance",
      +  "ifu",
      +  "social",
      +  "penalty",
      +  "general"
      +]
  2. Added

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, the description discloses data provenance (2026 DGT codes, checked 20 October 2026), a behavioral rule (holidays shift deadlines to the next working day), completeness limits (not exhaustive; extensions absent), and error semantics (country_not_available, key_required without an API key). This is unusually rich behavioral disclosure.

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 is front-loaded and useful, but the body is a ~300-word enumeration of every individual obligation, article number and penalty percentage. That content belongs in the tool's returned data, not in a description whose job is selection and invocation; it buries the operational guidance.

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 burden of describing the return shape, and it does: each item includes who must file, the deadline text, its article and the official source. Combined with filter semantics and error behavior, an agent has enough to call and interpret the result correctly.

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 all four parameters are already documented. The description adds a couple of q examples ('IFU', 'CNAS') but mostly restates the treatment enum verbatim, so it does not meaningfully extend the schema. 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 line names a specific verb and resource ('Get the legal filing and payment deadlines of businesses in Algeria') and immediately enumerates the categories it covers, so an agent can distinguish it from siblings like get_tax_rates or get_tax_code_article without reading the 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 clear context: filter by q and treatment, Algeria only, with an explicit pointer to list_countries for other datasets. It also warns the list is not exhaustive and that DGI extensions are excluded. What's missing is explicit routing against the closest siblings (e.g., when to use get_tax_code_article instead for full article text).

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.