Malja MCP

Official

by marsaplatform

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Durable solutions

durable_solutions

Read-only

Retrieve annual UNHCR refugee returns, resettlement, naturalisation, and IDP returns by country, with origin/asylum roles and optional per-capita normalization.

Instructions

UNHCR durable solutions per year: refugee returns, resettlement, naturalisation and IDP returns. These are FLOWS during each year (not end-year stocks), so a period total is reported. role "origin" (default) = solutions for people FROM the country (returns home, resettled/naturalised abroad); role "asylum" = refugees who left the country to return home, people resettled TO it, naturalised IN it. Optional other_country cross-filter and normalize_by ("population" → per 1,000 residents of the country).

Input Schema

TableJSON Schema

Name	Required	Description
`role`	No	"origin" (default) = solutions for people from the country; "asylum" = solutions in / departures from the country as host or resettlement country
`locale`	No	Language of the human-readable text output: "en" (default) or "ar" (Modern Standard Arabic, right-to-left). Structured JSON fields, ISO3 codes and dataset ids stay in English either way.
`country`	Yes	Country name or ISO3 code, e.g. "Egypt", "EGY", "syria"
`year_to`	No	Last year of the range (default: latest available)
`year_from`	No	First year of the range (default: 10 years back)
`normalize_by`	No	Normalize values by a denominator: "population" → per 1,000 residents, "gdp" → per US$1bn GDP. Requires the worldbank provider.
`other_country`	No	Optional second country for the opposite role, e.g. country="Syria", other_country="Lebanon" → Syrians returning from Lebanon

Output Schema

TableJSON Schema

Name	Required	Description	Default
`role`	Yes
`unit`	Yes
`years`	Yes
`source`	Yes
`country`	Yes
`measure`	Yes
`year_to`	Yes
`year_from`	Yes
`country_code`	Yes
`normalize_by`	Yes
`period_total`	Yes
`period_totals`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Oct 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint, so the description carries real weight: it discloses that values are period totals rather than point-in-time stocks, and that normalize_by requires the worldbank provider. It stops short of describing pagination or coverage limits, but the flow semantics are the key non-obvious trait.

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?

Core concept (flows vs stocks) is front-loaded and the three dense sentences are mostly load-bearing. The role parenthetical duplicates schema content and makes it slightly heavier than needed.

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?

For a 7-parameter tool with an output schema, the description covers the unusual semantics (flows, role inversion, cross-country filtering, normalization) that an agent could otherwise misread. Return values are properly left to the output schema.

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 coverage is 100%, so every parameter is already documented in the schema. The description's role explanation and the other_country example largely restate the enum descriptions, adding only marginal value beyond the structured fields.

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 resource (UNHCR durable solutions) and enumerates its components (refugee returns, resettlement, naturalisation, IDP returns). The explicit 'FLOWS during each year (not end-year stocks)' note distinguishes it from stock-oriented siblings like refugee_population without the agent needing to open the schema.

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?

Clearly frames the tool's domain by contrasting annual flows against end-year stocks, which steers the agent away from refugee_population. It explains role=origin vs asylum selection, but names no explicit when-not conditions or alternative tools.

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