Skip to main content
Glama

UpGrowth: business data for Algeria, Tunisia and Morocco

by io.github.Z4KARY
OverviewDiscussionsAdmin

Search Journal Officiel titles

search_jo_titles
Read-only

Search the official titles of the texts listed in the summaries (sommaires) of the Algerian Journal Officiel: laws, ordinances, decrees, orders and notices. Each match gives the year and issue number, the section heading, the title and the links to the issue page and to its official PDF. Use it to find when and where a text was published. Only the issues whose summary UpGrowth holds are searched: every year from 1962 to today (without an API key, only the current year and the two before it, and at most 10 matches: meta.free_years and meta.truncated say so; meta.sommaire_years lists the years searched). The summaries of 1962 to 2001 are read from the scanned issues: a title is listed only when two of three independent readings give it word for word (the third, by Opus, settles what the first two dispute), 98 % of the entries, so an empty result does not prove that a text does not exist (search_jo_text searches their full text too), and those hits have no upgrowth.dz page (url is null, pdf_url links the official scan). Optionally restrict it to one year. Returns a page of matches; meta.total is their number. Algeria only: no Moroccan summaries are held yet, so country MA returns country_not_available, and so does country TN.

Input Schema

NameRequiredDescriptionDefault
qYesWords to look for in the official titles of the texts, for example loi de finances 2026. Every word must start a word of the title; accents and letter case are ignored. From 2 to 100 characters.
langNoLanguage of the labels, notes and attribution text in the answer: fr (French, the default), ar (Arabic) or en (English).fr
yearNoSearch only the issues of this year (1962 or later). Leave it out to search every year. Without an API key only the current year and the two before it can be searched; older years come with a paid plan.
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.
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
    • changedInput schema / properties / year / description
      Previous value: -"Search only the issues of this year (1962 or later). Leave it out to search every year. Without an API key only the current year and the two before it can be searched."New value: +"Search only the issues of this year (1962 or later). Leave it out to search every year. Without an API key only the current year and the two before it can be searched; older years come with a paid plan."
  2. 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 / 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."
    • changedInput schema / properties / year / description
      Previous value: -"Search only the issues of this year (1962 or later). Leave it out to search every year."New value: +"Search only the issues of this year (1962 or later). Leave it out to search every year. Without an API key only the current year and the two before it can be searched."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Well beyond the readOnlyHint annotation, it discloses corpus coverage (1962–today), free-tier caps (current year + two prior, max 10 matches), the meta fields that report those caps, the two-of-three OCR arbitration rule behind 1962–2001 entries, and that those hits have url=null and a scan PDF. This is unusually rich behavioral context for a read tool.

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?

The key scoping facts (what is searched, coverage, caps, OCR caveat) are front-loaded and each sentence carries information. However, it is delivered as one very dense paragraph with some restatement of schema-level facts (country codes, year bounds), which makes it heavier than necessary.

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 (year, issue number, section heading, title, issue page and PDF links, meta.total) and the important edge cases (empty result ambiguity, null url for scanned years, country_not_available/key_required). Nothing an agent needs to interpret results correctly is missing.

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 description coverage is 100%, so the schema already documents every parameter, and the description largely restates it. It does add modest semantic value by framing year as an optional narrowing ('Optionally restrict it to one year') and by surfacing meta.total as the pagination anchor, but does not supplement the q matching rules or limits beyond what the schema says.

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 ('Search the official titles of the texts listed in the summaries of the Algerian Journal Officiel') and enumerates the text types covered. It is clearly distinguishable from siblings like search_jo_text (full text), get_jo_act and list_jo_issues.

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?

Gives an explicit use case ('find when and where a text was published') and an explicit alternative route: an empty result does not prove absence, so use search_jo_text for full text. It also states the country exclusion (MA/TN return country_not_available) rather than leaving it to inference.

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