Skip to main content
Glama

Statistics of the World

by com.statisticsoftheworld

get_indicator_ranking

Rank countries by an indicator available to the caller's tier. Supports top N and bottom N queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results (default 10)
orderNo"desc" for highest first, "asc" for lowest first
indicator_idYesIndicator ID. GDP accepts IMF.NGDPD or the World Bank original NY.GDP.MKTP.CD; also e.g. SP.POP.TOTL for population, FP.CPI.TOTL.ZG for inflation. Call get_available_indicators or search_indicators to browse the listed catalog.

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / indicator_id / description
      Previous value: -"Indicator ID (e.g., NY.GDP.MKTP.CD for GDP, SP.POP.TOTL for population, FP.CPI.TOTL.ZG for inflation)"New value: +"Indicator ID. GDP accepts IMF.NGDPD or the World Bank original NY.GDP.MKTP.CD; also e.g. SP.POP.TOTL for population, FP.CPI.TOTL.ZG for inflation. Call get_available_indicators or search_indicators to browse the listed catalog."
  2. Changed1 schema field changed
    • changedInput schema / properties / indicator_id / description
      Previous value: -"Indicator ID (e.g., IMF.NGDPD for GDP, SP.POP.TOTL for population, IMF.PCPIPCH for inflation)"New value: +"Indicator ID (e.g., NY.GDP.MKTP.CD for GDP, SP.POP.TOTL for population, FP.CPI.TOTL.ZG for inflation)"
  3. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the burden. It discloses tier-based availability and top/bottom support, but does not explain return format, missing data behavior, or potential errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with clear front-loaded purpose, no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives a basic overview but lacks output format details and edge-case behavior, leaving the agent uncertain about the response structure.

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

Parameters3/5

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

All three parameters are well-described in the schema, and the description adds nothing beyond the schema. Baseline 3 applies due to high schema coverage.

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 a specific action (rank countries) and resource (indicator available to the caller's tier), distinguishing it from sibling tools like get_historical_data or search_indicators by focusing on ranking/ordering.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for ranking queries but does not explicitly state when to prefer this over alternatives like get_historical_data or compare_countries, nor does it mention exclusions.

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

All Statistics of the World 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.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but get_historical_data and get_series_data can overlap for monthly series, and compare_countries versus get_indicator_ranking both offer cross-country comparisons. Detailed descriptions mitigate most ambiguity.

Naming Consistency4/5

All tools use a verb_noun pattern in snake_case, but list-like operations are inconsistently named (e.g., get_available_indicators and get_country_list use get_ while list_series uses list_). Overall, the pattern is predictable.

Tool Count5/5

With 11 tools, the server is well-scoped. It covers discovery (search/list), retrieval (country overview, series), comparison, ranking, and calendar features without unnecessary bloat.

Completeness4/5

The tool set covers indicator discovery, country metadata, historical and high-frequency data, comparisons, ranking, and release calendar. Minor gaps exist (e.g., no dedicated indicator metadata tool) but core workflows are supported.

Resources