Skip to main content
Glama
lpicci96

unesco-mcp

by lpicci96

get_time_series

Retrieve the complete time series for a UNESCO UIS indicator by country or region. Filter by year range to analyze trends and visualize data changes over time.

Instructions

Get the full time series for a UNESCO UIS indicator for one country or region.

Returns all data points for the indicator × geography combination, optionally filtered to a year range. Ideal for trend analysis and time-series visualisation.

GEOGRAPHY RULES:

  • For countries: pass the ISO3 code directly (e.g. "KEN", "FRA").

  • For regions: ALWAYS call search_geo_units first — it will ask the user which grouping system to use. Regional names map to multiple codes with different country compositions; using the wrong one gives silently wrong data.

  • If omitted, the tool will interactively ask the user for the geography.

Args: indicator_code: The indicator code (e.g. "LR.AG15T99"). geo_unit_code: ISO3 code for countries, or a confirmed code from search_geo_units for regions. Omit to trigger interactive geography lookup. start_year: Optional. First year to include (inclusive). end_year: Optional. Last year to include (inclusive).

Returns: A dictionary with: - "indicator_code", "indicator_name": Indicator identity. - "geo_unit_code", "geo_unit_name": Geography identity. - "data_points": Chronological list of {year, value, qualifier}. - "summary": {total_data_points, min_value, max_value, latest_year, note}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indicator_codeYes
geo_unit_codeNo
start_yearNo
end_yearNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description carries full burden. It discloses behavior: returns all data points, optional year range, geography rules including risks, and return structure. Comprehensive.

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?

Well-structured with sections and front-loaded purpose. Slightly verbose but all content is valuable. Could be trimmed slightly, but still effective.

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?

Given the complexity (4 params, 1 required, no annotations, but has output schema), the description is very complete. Covers geography rules, parameter usage, and return format thoroughly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, but description explains each parameter in detail: indicator_code, geo_unit_code with rules, start_year, end_year. Adds significant meaning beyond schema types.

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?

The description clearly states the tool gets the full time series for a UNESCO UIS indicator for one country or region. It distinguishes from siblings by mentioning geography rules and referencing search_geo_units for regions.

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 states when to use (trend analysis, time-series visualization) and provides geography rules with a clear directive to use search_geo_units for regions to avoid silent errors.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lpicci96/unesco-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server