Skip to main content
Glama

UpGrowth: business data for Algeria, Tunisia and Morocco

Search the full text of the Journal Officiel

search_jo_text
Read-only

Search the full text of the acts published in the Algerian Journal Officiel since 1962 (French edition: laws, ordinances, presidential and executive decrees, orders, decisions, Bank of Algeria regulations, corrigenda), not only their titles. Each match gives the year, the issue, the place of the act in the issue (ord), its type, its number when it has one, its title, its first page, an excerpt around the words and the links to the issue page and the official PDF; get_jo_act then returns the whole text. Words are matched in French with accents and case ignored and plurals folded (for example "redevance dossiers investissement"); quotes search an exact phrase, OR offers alternatives and a leading minus excludes a word. Best matches first. Use it to find which text sets a rule, a rate, an amount or a procedure, then read that text with get_jo_act before quoting it. The text is the official one as published: an act amended since appears as it was printed. From 2002 the text is the one of the official PDF (source pdf); from 1962 to 2001 it was read from the scans by three independent machine readings, each word kept when two of them agree (source scan), and a passage no two readings gave alike is marked [[? ... ?]] (uncertain counts them in an act): check such a passage on the PDF before quoting it. Without an API key, only the current year and the two before it, and at most 10 matches (meta.free_years, meta.truncated). Algeria only (country DZ); other countries return country_not_available.

Input Schema

NameRequiredDescriptionDefault
qYesWords to find in the text, accents and case ignored, for example redevance traitement dossiers investissement, or a phrase in quotes.
langNoLanguage of the labels, notes and attribution text in the answer: fr (French, the default), ar (Arabic) or en (English).fr
typeNoOnly the acts of this kind.
yearNoOnly the acts published that year (2002 or later).
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. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds a great deal beyond them: 1962–2001 scan vs 2002+ PDF provenance, [[? ... ?]] uncertainty markers, free-tier caps (current year + two, max 10 matches, meta.free_years/meta.truncated), Algeria-only with country_not_available/key_required errors. This goes well past the safety hints, so it earns more than the annotation baseline.

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?

Purpose and search syntax are front-loaded, followed by match fields, provenance caveats and limits. Dense but nearly every sentence earns its place; the parenthetical enumeration of act types is heavy but informative for this domain.

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 compensates by enumerating the returned fields (year, issue, ord, type, number, title, page, excerpt, links) and covering error/limit behavior and source-reliability caveats. An agent has everything needed to call and interpret it correctly.

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 baseline is 3, but the description adds query semantics the schema does not: plural folding, OR alternatives, and a leading minus to exclude. It also reinforces the country restriction in prose, adding meaning beyond the enum.

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 full text of the acts published in the Algerian Journal Officiel since 1962') and explicitly contrasts with the sibling search_jo_titles ('not only their titles'). An agent can immediately tell it apart from title-search and other JO tools.

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 a concrete use case ('find which text sets a rule, a rate, an amount or a procedure') and names the follow-up tool explicitly ('then read that text with get_jo_act before quoting it'). The when-to-use path and the alternative for full text are both spelled out.

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.