ilostat-mcp-server

Search ILOSTAT indicators

ilostat_search_indicators

Read-onlyIdempotent

Search ILOSTAT's catalog of labour-statistics indicators by plain-language terms and filters. Each hit is one indicator with its datasets — one per available frequency (annual, quarterly, monthly) — plus breakdowns, coverage years, number of reference areas, source database, and last update; pass a dataset ID to ilostat_describe_indicator for its units and breakdown codes, then to ilostat_query_indicator or ilostat_compare_geographies for values. Every search term must match a word or word prefix in the indicator's label, subject, database, breakdown names, code, or definition; British and American spellings (labour/labor) match alike. Facet counts reflect all applied filters.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Hits per page (1–50).
`query`	No	Plain-language terms, e.g. "youth unemployment" or "informal employment rate". Case, accents, and punctuation are ignored, labor matches labour, and a trailing plural s is tolerated. Omit to browse by filters (results then order by indicator code).
`cursor`	No	Opaque continuation token: the previous page's next_cursor, passed unchanged.
`subject`	No	Subject code, e.g. LUU (unemployment and labour underutilization); case-insensitive. ilostat_list_reference topic subjects lists them.
`database`	No	Source database code, e.g. LFS or ILOEST (the ILO modelled estimates); case-insensitive. ilostat_list_reference topic databases lists them.
`breakdown`	No	Classification type the indicator is broken down by, e.g. AGE, ECO, GEO, SEX; case-insensitive. ilostat_list_reference topic classification_types lists them.
`frequency`	No	Keep only datasets of this frequency: A annual, Q quarterly, M monthly. Narrows each hit's datasets; an indicator with none left drops out.
`aggregates_only`	No	Keep only datasets carrying World, regional, or income-group rows, dropping indicators with none.

Output Schema

TableJSON Schema

Name	Required	Description
`cap`	No	The limit applied to this page.
`hits`	No	This page of hits. With a query: tier, then more reference areas first, then code. Without: by code.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Hits returned on this page.
`total`	No	Indicators matched after all filters.
`facets`	No	Counts over the fully filtered match set, not just this page.
`notice`	No	Why the query was browsed by filters alone, how to widen a search that matched nothing, that the cursor starts past the last match, and how to reach the remaining pages — whichever apply, joined.
`truncated`	No	True when more hits remain beyond this page.
`next_cursor`	No	Pass as cursor to get the next page; absent on the last page.
`catalog_as_of`	No	ISO timestamp the searched catalog was last confirmed current.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description adds substantive behavioral detail beyond them: matching is word/prefix based across label, subject, database, breakdown names, code, and definition; British and American spellings match alike; facet counts reflect all applied filters. These are non-obvious search semantics the agent could not infer from annotations or schema.

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 purpose and return shape, then the workflow, then matching semantics. The first sentence is long and packs several clauses, but every sentence carries information with no filler or repetition.

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 an 8-parameter, zero-required search tool with an output schema, the description covers the non-obvious behavior: return shape, matching rules, spelling tolerance, filter-as-query fallback, and downstream tool routing. Nothing an agent needs to invoke it correctly 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 baseline is 3, but the description adds meaning beyond the schema: it clarifies the AND semantics of multiple terms, prefix matching, the frequency-to-datasets relationship ('an indicator with none left drops out'), and that filters can substitute for a query. This is value beyond the parameter descriptions.

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 ('Search ILOSTAT's catalog of labour-statistics indicators') and immediately describes what a hit contains. It distinguishes itself from siblings by naming ilostat_describe_indicator, ilostat_query_indicator, and ilostat_compare_geographies as the downstream steps, so an agent knows this is the entry-point search, not a query tool.

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 explicit workflow guidance: pass a dataset ID to describe_indicator, then to query_indicator or compare_geographies for values, and 'Omit to browse by filters'. It does not name exclusions (e.g. use ilostat_list_reference for code discovery) beyond the schema hints, so it stops short of full when/when-not coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ilostat-mcp-server tools Inspect

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.