Skip to main content
Glama

UpGrowth: business data for Algeria, Tunisia and Morocco

by io.github.Z4KARY
OverviewDiscussionsAdmin

List customs tariff sections

customs_tariff_sections
Read-only

List the sections of the Algerian customs tariff, the first level of the harmonized system classification of goods, each with its Roman numeral, its title and the range of its chapters. For Algeria the tariff is not printed in the Journal officiel (ordonnance 01-02 has it published apart by the finance ministry): meta.sources cites the acts behind it and meta.status_note marks the titles À VÉRIFIER. Use it to locate a family of products before listing the chapters of a section. For Tunisia (country TN) it lists the sections of the Tunisian customs tariff, with the titles in French read on the site of the General Directorate of Customs (douane.gov.tn); Tunisia needs an API key. For Morocco (country MA) it lists the 21 sections of the harmonized system 2022 in French (the ADII tariff adopts it; MA needs an API key). This dataset holds no duty rates and no tariff lines below the chapter level.

Input Schema

NameRequiredDescriptionDefault
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, but the description discloses substantial behavioral detail: meta.sources attribution, meta.status_note marking titles as 'À VÉRIFIER', API key requirements (TN/MA need keys, only DZ answers otherwise), and the country_not_available/key_required error outcomes.

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?

Front-loaded with the core purpose and returned fields, then per-country behavior and limitations. Some redundancy with the schema's country parameter description on API keys and error codes, but each sentence generally earns its place and no filler is present.

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 explains the returned fields and the boundaries of the dataset (no duty rates, no tariff lines below chapter level), plus attribution and verification metadata. 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 the schema already documents lang and country fully, including defaults, enum values, ISO code format, and error behavior. The description largely restates the same country/key semantics rather than adding new meaning, so the 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?

States a specific verb+resource ('List the sections of the Algerian customs tariff, the first level of the harmonized system classification of goods') and enumerates the returned fields (Roman numeral, title, chapter range). This clearly distinguishes it from the sibling customs_tariff_chapters tool.

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?

Explicitly routes: 'Use it to locate a family of products before listing the chapters of a section,' naming the downstream alternative. Adds when-not guidance ('This dataset holds no duty rates and no tariff lines below the chapter level') and per-country conditions for TN/MA versus DZ.

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