Skip to main content
Glama

Unesco Uis

by io.github.pipeworx-io
OverviewAdmin

Get Data

get_data
Read-onlyIdempotent

Fetch UNESCO UIS statistic values: education, literacy, school enrollment/completion, science (R&D) and culture indicators. Returns {records:[{indicatorId,geoUnit,year,value}]}. Indicator IDs come from list_indicators; geoUnit is an ISO3 country code (e.g. "BRA") from list_geounits. Both accept one or many (comma-separated) values; empty records means no data for that indicator/country/year combination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoLast year (inclusive), e.g. 2020.
startNoFirst year (inclusive), e.g. 2015.
geoUnitYesISO3 country/region code(s) from list_geounits, e.g. "BRA". Multiple comma-separated: "BRA,ARG".
indicatorYesIndicator ID(s) from list_indicators, e.g. "CR.1" or "10". Multiple comma-separated: "CR.1,CR.2".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "end": 2020,
+    "geoUnit": "BRA",
+    "indicator": "CR.1",
+    "start": 2015
+  },
+  {
+    "geoUnit": "BRA,ARG,CHL",
+    "indicator": "10,11"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the tool as read-only and idempotent. The description adds the return format structure and explains that empty records indicate no data, providing useful behavioral context beyond annotations.

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 description is concise and front-loaded, efficiently covering purpose, return format, and parameter usage in one paragraph. Minor improvement could be structuring with bullet points.

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?

Despite lacking an output schema, the description fully explains the return format and covers parameter usage, examples, and edge cases (empty records). It is complete for a data retrieval tool with good annotation coverage.

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?

With 100% schema coverage, the description adds value by connecting parameters to sibling tools (list_indicators, list_geounits) and clarifying comma-separated input, which goes beyond the schema's 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?

The description clearly states the tool fetches UNESCO UIS statistic values for specific domains (education, literacy, etc.), specifies the return format, and relates to sibling tools like list_indicators and list_geounits.

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?

The description explains that indicator IDs come from list_indicators and geoUnit from list_geounits, which provides usage context. However, it does not explicitly state when to use this tool versus others or provide alternative scenarios.

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

All Unesco Uis toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources