Skip to main content
Glama

unhcr-refugees-mcp-server

UNHCR durable solutions

unhcr_get_solutions
Read-onlyIdempotent

Get durable solutions per year (1959 to the latest year) by country of origin and/or asylum: refugees who returned home, refugees resettled to a third country, refugees naturalised, and IDPs who returned. The asylum country means something different per column: the country refugees returned from, the country they were resettled to, the country that naturalised them; IDP returns sit on the origin country itself. Null means the figure was not collected for that country and year, not zero.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows 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.
stageNoStage 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.
asylumNoCountry 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.
expandNoList 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
originNoCountry 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_byNoOrder of the full result before the inline cut. year (default) orders by year, then origin ISO3, then asylum ISO3; a count field orders largest first, nulls last.year
year_toNoLast 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_fromNoFirst 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoThe limit that was applied.
rowsNoInline rows, sorted, up to limit.
errorNoPresent when the call failed. Absent on success.
shownNoRows returned inline.
noticeNoGuidance for this result: empty-result hints, year clamps, where the full set was staged, or how to narrow.
datasetNoPresent when the full result was staged as a dataframe; read its columns with unhcr_dataframe_describe, then query it with unhcr_dataframe_query.
measureNostock: people in a situation on 31 December; flow: events during the year.
completeNoFalse when the server row cap stopped the upstream fetch; the notice says how many upstream rows were fetched and how to narrow.
footnotesNoUNHCR caveats matching rows of the full result, country-specific first; at most 20.
truncatedNoTrue when rows were cut at limit.
data_notesNoHow to read the counts: stock or flow, rounding, the meaning of null, caveats.
total_rowsNoRows 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.
attributionNoAttribution UNHCR requires when these figures are reused.
latest_yearNoNewest year this dataset publishes.
applied_scopeNoThe scope actually sent upstream, including clamped years and code rewrites.
footnotes_totalNoCaveats matching the full result, before the cap.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so credit goes to the extra interpretive context the description supplies: that 'asylum' denotes a different country per measure (returned-from, resettled-to, naturalising country) while IDP returns sit on the origin country, and that null means 'not collected', not zero. These are non-obvious data behaviours that prevent real misinterpretation.

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?

Purpose leads, and all three sentences carry information that is not restated structurally — nothing is padding. The middle sentence about asylum meaning per column is dense and would read better as a short list, but the ordering is logical and front-loaded.

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?

With an output schema present, a fully documented 8-parameter schema and annotations covering read-only/idempotent behaviour, the description only needed to supply purpose, dimension semantics and null handling — all of which it does. An agent has everything required to call and interpret this tool correctly.

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 description coverage is 100%, so the baseline is 3; the description adds meaning beyond the schema by explaining the conceptual asymmetry of the origin/asylum dimensions and how they relate to the returned measures, which the schema's per-parameter text does not convey. It adds no detail on limit/stage/sort_by beyond what the schema already documents.

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 and resource ('Get durable solutions per year') and immediately enumerates the four measures it returns (returned refugees, resettlement, naturalisation, IDP returns), which cleanly separates it from siblings like unhcr_get_population, unhcr_get_demographics and unhcr_get_asylum_applications. The year coverage (1959 to latest) and the origin/asylum slicing dimensions are explicit.

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?

Usage is only implied through content — the agent can infer this is the tool for durable-solutions figures, but there is no explicit when-to-use/when-not statement and no sibling is named as an alternative for population, demographics or asylum-applications data. The only routing hint (resolve names via unhcr_list_reference) lives in the schema, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.