Skip to main content
Glama

UpGrowth: business data for Algeria, Tunisia and Morocco

by io.github.Z4KARY
OverviewDiscussionsAdmin

Get the full text of a Journal Officiel act

get_jo_act
Read-only

Get the full text of one act of the Algerian Journal Officiel published since 1962, by its number (for example 22-299, with type when a law and a decree share the number) or by year, issue and ord as search_jo_text returns them. Returns its type, number, title, first page, the links to the issue page and the official PDF, the text itself in parts of 20,000 characters (part, parts, chars: ask the next part to read on), and named_in_titles: the earlier or later acts whose title names this one, such as the decrees amending or completing it, its corrigenda and its implementing texts (the newest 50, listed oldest first, with named_in_titles_total and named_in_titles_truncated; each carries a relation, amends, completes, repeals, applies, approves, corrects or cites, read from its title alone, with relations counting them, repealed_by listing the acts whose title says they repeal this one and last_amended_by the newest listed act whose title amends or completes it (or null), never a statement that the act is in force or repealed). Also returns amends: the acts that this act's title says it modifies, completes or repeals, with their place in the Journal officiel when held (null fields when not), and status_hint: repealed_by_later_act, amended or null, read from the titles only. Check named_in_titles before quoting an article: the text is the one published in that issue, not a consolidated version. For 1962 to 2001 (source scan) the text was read from the scan: a passage between [[? and ?]] is not settled yet (uncertain counts them), check it on pdf_url before quoting it; the page is the page of the scan. Without an API key, only the acts of the current year and the two before it. Algeria only (country DZ); other countries return country_not_available.

Input Schema

NameRequiredDescriptionDefault
ordNoThe place of the act in its issue, as search_jo_text returns it.
langNoLanguage of the labels, notes and attribution text in the answer: fr (French, the default), ar (Arabic) or en (English).fr
partNoWhich part of the text, 1 by default; parts says how many there are.
typeNoThe kind of act, needed when several acts carry the number (a law and a decree, for example).
yearNoThe year of the issue (with issue and ord), or to narrow a number.
issueNoThe number of the issue within its year, as search_jo_text returns it.
numberNoThe number of the act as the Journal Officiel prints it, for example 22-299 or 26-06.
articleNoOne article of the act, for example 25, 1er, 87 bis or 715 bis 133: returns only that article (article, article_text) instead of the parts. It is the article as printed in that issue, not consolidated: named_in_titles still lists the acts that amended it. For 1962 to 2001 scans the [[? ... ?]] marks stay as they are. not_found when the heading is not recognised: read the parts then.
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
    • addedInput schema / properties / article
      Added value: +{
+  "description": "One article of the act, for example 25, 1er, 87 bis or 715 bis 133: returns only that article (article, article_text) instead of the parts. It is the article as printed in that issue, not consolidated: named_in_titles still lists the acts that amended it. For 1962 to 2001 scans the [[? ... ?]] marks stay as they are. not_found when the heading is not recognised: read the parts then.",
+  "maxLength": 20,
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say readOnly/openWorld=false; the description adds the auth tier (no key = current year plus two), the country gating, the 20,000-character part chunking with part/parts/chars continuation, the 50-item truncation on named_in_titles with a truncated flag, null semantics for missing fields, and the [[? ... ?]] scan-uncertainty convention. It also explicitly warns that status_hint is read from titles alone and is never a statement of whether the act is in force or repealed.

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?

Purpose is front-loaded correctly, but the body is one dense run-on paragraph with deeply nested parentheticals that enumerate return fields. With no output schema the information is necessary, yet the packing makes it hard to scan and the output-field inventory competes with the calling instructions.

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?

For a 9-parameter, zero-required, output-schema-less tool, the description covers the return shape (type, number, title, page, links, text parts, named_in_titles, amends, status_hint), error cases, pagination, and access tiers. An agent has everything needed to call it and interpret the result.

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 coverage is already 100%, so the baseline is 3; the description earns above that by explaining the part-chaining loop ('ask the next part to read on') and the number-plus-type disambiguation as a coherent lookup recipe rather than a field list. Much of the rest restates what the schema already documents.

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 ('get the full text of one act of the Algerian Journal Officiel'), plus scope ('published since 1962') and jurisdiction ('Algeria only'). It also distinguishes itself from the retrieval path by naming the sibling that supplies the identifiers ('as search_jo_text returns them').

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?

Gives clear preconditions: obtain identifiers via search_jo_text, supply type when a law and decree share a number, and check named_in_titles before quoting since the text is not consolidated. It also states the no-API-key restriction and the country_not_available outcome. What it never does is contrast itself with the closest unmentioned alternative, get_jo_issue, for issue-level reading.

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