unhcr-refugees-mcp-server

UNHCR demographics

unhcr_get_demographics

Read-onlyIdempotent

Get UNHCR year-end stocks (2001 to the latest year) broken down by population type, sex, and age band (0–4, 5–11, 12–17, 18–59, 60+, unknown age), by country of origin and/or asylum. Coverage is partial: each row gives the share of its total that UNHCR could disaggregate by sex, and age bands are null where no breakdown exists. These totals come from a separate collection and need not match unhcr_get_population.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Rows returned inline, 1–500 (default 100). Sorting runs over the full result first; a larger result is staged as a dataframe where dataframes are enabled.
`stage`	No	Stage the full result as a dataframe even when it fits inline, e.g. to join it with another unhcr_get_* result in unhcr_dataframe_query. Where dataframes are unavailable it is ignored, and the notice says so.
`asylum`	No	Country of asylum — where people sought or hold protection; for returns, the country they returned from — as ISO3 codes (DEU, TUR), case-insensitive, same rules as origin. At most 50 codes. Omit to sum every asylum country into one row, or set expand to list each.
`expand`	No	List every country, one row each, for a dimension that origin or asylum leaves unfiltered: origin, asylum, or both. Default none, where an unfiltered dimension is summed into one row. Expanding a dimension that origin or asylum already filters is rejected.	none
`origin`	No	Country of origin — where people fled from — as ISO3 codes (SYR, AFG), case-insensitive. ISO 3166 alpha-2 codes (SY) are rewritten to ISO3 and echoed in applied_scope. UNHCR's own codes (GFR) are rejected with the ISO3 to pass instead, and country names are rejected: resolve a name with unhcr_list_reference (topic countries, name_contains). Each listed code returns its own rows; codes are never summed together. At most 50 codes. Omit to sum every origin into one row, or set expand to list each.
`sort_by`	No	Order of the full result before the inline cut. year (default) orders by year, then origin ISO3, then asylum ISO3, then population type; total orders largest first, nulls last.	year
`year_to`	No	Last year of the window. When omitted, the window runs to the latest published year (latest_year in the result). A year past the latest published year is clamped to it and the clamp is reported.
`year_from`	No	First year of the window. When omitted, the window starts at the dataset's first year. A year before the dataset's first year is clamped to it and the clamp is reported; a window entirely outside the dataset's years is rejected.
`population_types`	No	Keep only these population types, case-insensitive: REF refugees, ASY asylum-seekers, OIP other people in need of international protection, IDP internally displaced, STA stateless, OOC others of concern, HST host community, RET returned refugees, RDP returned IDPs. Decode them with unhcr_list_reference (topic population_types). Omit for every type.

Output Schema

TableJSON Schema

Name	Required	Description
`cap`	No	The limit that was applied.
`rows`	No	Inline rows, sorted, up to limit.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Rows returned inline.
`notice`	No	Guidance for this result: empty-result hints, year clamps, where the full set was staged, or how to narrow.
`dataset`	No	Present when the full result was staged as a dataframe; read its columns with unhcr_dataframe_describe, then query it with unhcr_dataframe_query.
`measure`	No	stock: people in a situation on 31 December; flow: events during the year.
`complete`	No	False when the server row cap stopped the upstream fetch; the notice says how many upstream rows were fetched and how to narrow.
`footnotes`	No	UNHCR caveats matching rows of the full result, country-specific first; at most 20.
`truncated`	No	True when rows were cut at limit.
`data_notes`	No	How to read the counts: stock or flow, rounding, the meaning of null, caveats.
`total_rows`	No	Rows in the full result before the inline cut. When complete is false, the result is built from only the upstream rows fetched before the cap, so rows and summed counts can fall short of the complete result.
`attribution`	No	Attribution UNHCR requires when these figures are reused.
`latest_year`	No	Newest year this dataset publishes.
`applied_scope`	No	The scope actually sent upstream, including clamped years and code rewrites.
`footnotes_total`	No	Caveats matching the full result, before the cap.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld), and the description adds genuinely non-schema behavior: partial coverage, per-row disaggregation share, null age bands, and divergence from unhcr_get_population. It stops short of describing output shape or staging behavior in narrative form, but the caveats delivered are substantive.

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?

Three sentences, all front-loaded with the operation and its scope before the coverage caveats. Dense but every clause carries information; only marginal tightening is possible.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the description supplies the coverage caveat and sibling distinction an agent needs to interpret results correctly. It could still note the timeframe/limit interaction, but it is essentially complete for this complexity.

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?

Schema description coverage is 100%, so the schema already documents all nine parameters including code formats, clamping, and expand rules. The description adds essentially no parameter meaning beyond what the schema states, so the baseline 3 applies.

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 names a specific verb and resource (year-end stocks by population type, sex, age band) plus the dimensions of disaggregation and the source collection, and it explicitly contrasts itself with unhcr_get_population. An agent can distinguish it from siblings without opening schemas.

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?

It routes the agent to unhcr_get_population for consistent totals and notes that these numbers need not match, implying when to prefer each. However, it never states a positive when-to-use condition (e.g. 'use this when you need sex/age breakdowns'), so the guidance is contextual rather than explicit.

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

All unhcr-refugees-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.