Malja MCP

Official

by marsaplatform

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Compare countries

compare_countries

Read-only

Compare refugee or displacement metrics across 2–5 countries over a year range, with optional normalization per population or GDP for cross-country analysis.

Instructions

Compare a displacement metric across 2–5 countries over a year range. Defaults to refugees hosted (role "asylum") over the last 10 years. Set normalize_by to compare per 1,000 residents or per US$1bn GDP instead of absolute numbers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "countries": "<countries>"
    },
    "name": "compare_countries"
  }
}

Input Schema

Name	Required	Description
`role`	No	"asylum" = people hosted IN the country; "origin" = people displaced FROM the 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.
`metric`	No	Metric to compare, e.g. refugees, asylum_seekers, idps (default: refugees)
`year_to`	No	Last year of the range (default: latest available)
`countries`	Yes	Two to five countries to compare
`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.

Output Schema

Name	Required	Description	Default
`role`	Yes
`unit`	Yes
`metric`	Yes
`series`	Yes
`source`	Yes
`denominator`	No
`normalize_by`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.8.0Oct 29, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv0.7.0Oct 20, 2026

TDQS

A3.6/5.0

Behavior3/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's default behavior (asylum role, 10-year window) largely duplicates defaults already documented in the schema, and it adds no detail on rate limits, provider fallback, or what happens when a country is unknown.

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?

Three compact sentences, front-loaded with the core comparison scope followed by defaults and the normalization option. No filler or restatement of the title.

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?

With an output schema present, return values need not be explained, and the 7 parameters are fully documented in the schema. The description is sufficient to call the tool correctly, though it could mention locale behavior or metric availability to be fully self-contained.

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 description coverage is 100% and every parameter carries an enum or a documented default, so the schema does the heavy lifting. The description restates the 2–5 country bound and the normalize_by meaning but adds no syntax or edge-case guidance beyond the schema.

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 a specific verb and resource — comparing a displacement metric across 2–5 countries over a year range — which is concrete enough to distinguish it from single-country siblings like country_profile or search_country. It stops short of explicitly naming the alternatives (trend_analysis, top_host_countries) that an agent might confuse it with.

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 scope statement and the stated defaults (refugees hosted, last 10 years), so an agent knows what happens with no arguments. However, there is no explicit when-to-use / when-not guidance and no routing to alternatives such as trend_analysis or top_host_countries.

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