Skip to main content
Glama

Unhcr

by io.github.pipeworx-io
OverviewAdmin

Population

population
Read-onlyIdempotent

Forcibly displaced & stateless persons by year and country: refugees, asylum_seekers, idps (internally displaced), returned_refugees, returned_idps, stateless, others. Filter by coo (country of origin) and/or coa (country of asylum). coo_all/coa_all=true breaks the totals DOWN by that dimension (one row per origin or asylum country). NOTE: coo/coa take UNHCR's 3-letter code (e.g. Germany='GFR', not ISO3 'DEU') — resolve with list_countries first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coaNoCountry of ASYLUM — UNHCR 3-letter code (see list_countries.code).
cooNoCountry of ORIGIN — UNHCR 3-letter code (see list_countries.code).
pageNo1-based page; response.maxPages tells you the total.
limitNoRows per page (default 25).
yearToNoEnd year, inclusive.
coa_allNotrue = break results down per country of asylum.
coo_allNotrue = break results down per country of origin.
yearFromNoStart year, inclusive (data spans 1951+).

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: +[
+  {
+    "yearFrom": 2019,
+    "yearTo": 2023
+  },
+  {
+    "coa": "TUR",
+    "coa_all": true,
+    "coo": "SYR",
+    "yearFrom": 2020,
+    "yearTo": 2023
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds valuable behavioral context: it explains the breakdown behavior of boolean parameters (coo_all/coa_all break totals down by dimension) and warns about code format differences (UNHCR vs. ISO3). No contradictions with annotations.

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?

The description is a single, well-structured paragraph. It front-loads the main purpose, lists categories, then explains filtering and the important code note. Every sentence adds value with no repetition or fluff. Efficient and concise.

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?

Given the complexity of the tool (8 parameters, no output schema), the description covers the key aspects: categories, filtering, breakdown behavior, and code format. It does not describe the return format (e.g., paginated table), which is a minor gap, but the annotations and examples partly compensate. Overall, it is quite complete for a read-only data retrieval tool.

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 coverage is 100%, so baseline is 3. The description adds meaning by explaining the breakdown behavior of coo_all/coa_all ('breaks the totals DOWN by that dimension') and clarifying the code format for coo/coa. It also provides examples with parameters. This adds value beyond the schema definitions.

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 it retrieves data on forcibly displaced and stateless persons by year and country, with specific categories (refugees, asylum_seekers, etc.). The verb 'forcibly displaced & stateless persons by year and country' is specific, and it distinguishes itself from siblings like asylum_applications by focusing on population stocks rather than flows.

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 provides explicit guidance on using UNHCR 3-letter codes (not ISO3) and recommends using list_countries first. It explains the filtering by coo/coa and the breakdown behavior of coo_all/coa_all. However, it does not explicitly state when to use this tool vs. sibling tools like asylum_applications or asylum_decisions, leaving the comparison implicit.

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

All Unhcr 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