UNHCR Population Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_population_dataA | |
| get_demographics_dataA | |
| get_rsd_applicationsB | |
| get_rsd_decisionsA | |
| get_solutionsB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools are mostly distinct, covering demographics, population, RSD applications, RSD decisions, and solutions. However, get_demographics_data and get_population_data could be confused as both handle forcibly displaced populations, though demographics focuses on age/sex breakdowns while population covers types like refugees. Descriptions help clarify, but overlap exists.
All tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive nouns (e.g., get_demographics_data, get_population_data). This predictable naming makes it easy for agents to understand and navigate the toolset without confusion.
With 5 tools, the server is well-scoped for UNHCR population data, covering key aspects like demographics, population figures, RSD processes, and solutions. Each tool serves a clear purpose, avoiding bloat while providing comprehensive coverage for the domain.
The toolset covers core UNHCR data areas well, including demographics, population types, RSD applications/decisions, and solutions. A minor gap is the lack of tools for updating or managing data (e.g., CRUD operations), but this is reasonable for a read-only data query server focused on retrieval from an external API.