Skip to main content
Glama

UpGrowth: business data for Algeria, Tunisia and Morocco

by io.github.Z4KARY
OverviewDiscussionsAdmin

Search the post offices and ATMs of Algeria

search_post_offices
Read-only

Search Algérie Poste's post offices (kind post_office, the default) or ATMs (kind atm) by name or address words (q, accents ignored), by postal code (all five digits, or the first ones), by commune code, by wilaya, or around a place (lat and lng in decimal degrees, within radius_km, 10 by default: nearest first, with distance_km). Each post office comes with its class, address, postal code and former postal code, GPS position and commune; each ATM with whether it works. Use it to find the post office of a postal code, the offices of a delivery zone, or the nearest office or ATM to an address. Data read from Algérie Poste every day. Without an API key, at most 10 rows. Algeria only.

Input Schema

NameRequiredDescriptionDefault
qNoWords of the name or the address, accents ignored.
latNoLatitude of the place to search around, with lng.
lngNoLongitude of the place to search around, with lat.
kindNopost_office (default) or atm.
langNoLanguage of the labels, notes and attribution text in the answer: fr (French, the default), ar (Arabic) or en (English).fr
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.
wilayaNoA wilaya number from 1 to 69, or the slug of a wilaya created in 2026.
communeNoA four-digit commune code.
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
radius_kmNoSearch radius around lat and lng, in km (10 by default).
postal_codeNoA postal code, or its first digits (16 for every code of wilaya 16).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With readOnlyHint/openWorldHint already covering the safety profile, the description adds real behavioral context: data refreshed daily from Algérie Poste, the 10-row cap without an API key, the fact that paging requires a key, and the country_not_available / key_required error behaviors. It also discloses nearest-first ordering and the presence of distance_km in results.

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 search modes are front-loaded and each sentence carries information (matching modes, result fields, limits, region restriction). It is dense and long for a single block, but there is little filler.

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 returns and does so: each post office comes with class, address, postal code, former postal code, GPS position and commune, each ATM with operational status. Together with the limit/key notes and country restriction, nothing essential for a correct call 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 coverage is 100%, so the baseline is 3, but the description goes beyond the per-field schema text by explaining how parameters interact (lat/lng searched within radius_km, 10 by default, returned nearest-first with distance_km) and by clarifying that postal codes may be partial (all five digits or the first ones).

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 Algérie Poste's post offices ... or ATMs'), names the default kind, and covers the whole scope (Algeria only) in the opening sentence. No sibling tool touches postal data, so the agent can route to it unambiguously.

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 concrete when-to-use scenarios ('find the post office of a postal code, the offices of a delivery zone, or the nearest office or ATM to an address'). It does not name alternative tools or state exclusions, but no sibling overlaps, so the guidance is clear without being exhaustive.

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