Skip to main content
Glama

Forced displacement worldwide: UNHCR population statistics

get_displacement
Read-only

Free. UNHCR population statistics: refugees under UNHCR's mandate, asylum-seekers, internally displaced, stateless for the latest year (current year = preliminary mid-year) and the year before, plus the top 5 countries of origin of refugees in the last full year. These fields do not add up to UNHCR's headline total of forcibly displaced people.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_displacement"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the call is free, the current year is a preliminary mid-year figure, and the listed fields intentionally do not sum to UNHCR's headline forcibly-displaced total — a caveat that prevents a real analytical error.

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?

Two sentences, front-loaded with the cost note and the dataset name, then the field list and the summation caveat. Every clause carries information; the density is slightly high but no sentence is padding.

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 no input parameters and no output schema, the description carries the full burden of telling the agent what comes back, and it does so by enumerating the population categories and the year coverage. The summation warning closes the remaining ambiguity for a simple, low-risk read 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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument, drop-in call by describing fixed scope (latest year, prior year, last full year for origins).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact dataset and scope: UNHCR population statistics covering refugees under UNHCR's mandate, asylum-seekers, IDPs, and stateless persons, for the latest year plus the year before, plus top-5 refugee origin countries. That is far more specific than a restated title. It stops short of an explicit action verb, but for a zero-parameter getter the resource enumeration effectively is the purpose.

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 implied by the data scope rather than stated: an agent can infer this is the tool for forced-displacement headline figures. There is no explicit when-to-use, when-not-to-use, or named alternative among the siblings, and no guidance on whether to reach for it for country-level detail versus global totals.

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.