ILO Statistics (ILOSTAT) MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ilo_search_indicatorsA | Search the ILOSTAT catalogue of ~1,200 indicator dataflows by keywords in the name or id (e.g. "unemployment rate sex age"). All terms must match (AND, case-insensitive), so start with 2–3 English words and drop terms if you get 0 results. Everyday and US wording is resolved to the ILO's own (labor→labour, wages/salary→earnings, informality→informal, gender→sex, productivity→output per worker); when that happens the response says so in vocabulary_notes. Results are ranked by ILO relevance weight, not by match count. Reading the id tells you the shape: suffix _RT = rate/ratio, NB = number (usually thousands); dataflows whose second token starts with 2 (e.g. DF_UNE_2EAP…) are ILO modelled estimates with full country/year coverage, the others are reported national data. Returns dataflow ids to use with ilo_get_data / ilo_get_indicator_metadata. Searches the local catalogue only — it does not return statistical values (use ilo_get_data), does not search dimension codes such as countries (use ilo_list_dimension_values) and does not cover non-ILO sources. |
| ilo_get_indicator_metadataA | Structure of one ILOSTAT dataflow: dimensions (in SDMX key order), their codelists, the time dimension, the source's default selection and the data vintage (last update at the ILO). Use before ilo_get_data to know which filters exist. Does not return statistical values and does not list the codes themselves (use ilo_list_dimension_values). |
| ilo_list_dimension_valuesA | Valid codes (id + label) of one dimension of an ILOSTAT dataflow — e.g. the country/area codes of REF_AREA (ISO 3166-1 alpha-3 such as BRA, plus X-codes for aggregates such as X01 World) or the categories of SEX (SEX_T/SEX_M/SEX_F) and AGE. Use |
| ilo_get_dataA | Statistical observations from one ILOSTAT dataflow, filtered by dimension codes (filters, e.g. {"REF_AREA": ["BRA","ARG"], "SEX": "SEX_T"}) and period (start_period/end_period, e.g. "2015"/"2024"). REF_AREA is required, maximum 30 areas per call — for broad panels, split areas into batches and/or paginate by period. Unfiltered dimensions return all their categories. Does not aggregate, convert or otherwise transform values (raw ILOSTAT data only), and does not search indicators (use ilo_search_indicators). |
| searchA | Searches the ILOSTAT labour statistics (≈1,200 SDMX dataflows: employment, unemployment, wages, working time, informality, SDG labour indicators) catalog and returns up to 10 matching documents as { id, title, url }, ordered by relevance (an empty list means nothing matched). This tool exists for the OpenAI Deep Research contract: ChatGPT deep research, company knowledge and research workflows over the Responses API require exactly the tools Query: natural language or keywords, Portuguese or English; accents and case are ignored. Behavior: read-only and idempotent — the catalog comes from the public source and is cached in memory. |
| fetchA | Returns the full document for an id obtained from Companion of Behavior: read-only and idempotent — a live GET against the public source when the document needs it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ilo_country_labour_profile | Step-by-step workflow that assembles a labour-market profile of one country from ILOSTAT (unemployment, participation, employment ratio, informality, NEET, earnings, hours) with ILO citations. |
| ilo_compare_countries | Workflow that compares several countries (or regional aggregates) on one ILOSTAT indicator in a single data call, flagging modelled estimates versus reported data. |
| ilo_indicator_trend | Workflow that retrieves the time series of one ILOSTAT indicator for one country and describes the trend (first/last, peak/trough, breaks in series) with citations. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ilostat-guide | How to query ILOSTAT with this server: tool workflow, stable code conventions (REF_AREA ISO3 and X-aggregates, SEX, AGE, FREQ, dataflow id suffixes), limits and reporting rules. Read once per session to save discovery calls. |
| ilostat-key-dataflows | Verified dataflow ids for the most common indicators (unemployment, employment, participation, wages, working time, informality, NEET, SDG 8, productivity) — usable directly in ilo_get_data without searching. |
| ilostat-provenance | Meaning of every provenance field returned with the data (source_url, data_vintage, retrieved_at, notices, license, citation) and how to cite the ILO correctly. |
TDQS
Scored across 6 tools
The data tools (ilo_search_indicators, ilo_get_indicator_metadata, ilo_list_dimension_values, ilo_get_data) are clearly separated by function. The generic search and fetch tools are distinct from each other, but search and ilo_search_indicators both search the same catalog, creating mild overlap; their descriptions do clarify that one serves document retrieval and the other serves dataflow discovery.
The four ilo_* tools follow a consistent verb-based pattern with underscores, but the unprefixed generic tools search and fetch break the convention. The mixed prefixing is explainable but inconsistent across the set.
Six tools is a well-scoped size for the server's purpose: discovery, metadata inspection, dimension lookup, and data retrieval each have a dedicated tool. No tool feels redundant or unnecessary for the stated domain.
The tool set covers the full workflow needed to query ILOSTAT data: search for indicators, inspect metadata, list valid dimension codes, and retrieve data values. The search/fetch pair also enables document-level research, so there are no obvious dead ends in the intended use cases.