Malja MCP

Official

by marsaplatform

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Country profile

country_profile

Read-only

Get a one-call humanitarian snapshot for any country: latest hosted displaced population by category, people displaced from it, and top origin countries.

Instructions

One-call humanitarian snapshot of a country: latest displaced population hosted (by category), population displaced FROM the country, and its top origin countries.

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": {
      "country": "<country>"
    },
    "name": "country_profile"
  }
}

Input Schema

Name	Required	Description	Default
`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"

Output Schema

Name	Required	Description
`year`	No
`hosted`	Yes	Latest people-of-concern figures hosted in the country
`region`	No
`source`	Yes
`country`	Yes
`top_origins`	Yes
`country_code`	Yes
`displaced_abroad`	Yes	Latest figures for people displaced FROM the country

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.8.0Oct 29, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedOutput schema / properties / displaced_abroad / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / hosted / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
First observedv0.7.0Oct 20, 2026

TDQS

A3.8/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 safety is covered. The description adds useful behavioral context about the composite nature of the response ('one-call', 'latest', 'by category'), though it does not discuss data freshness, sourcing, or limitations.

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?

A single, front-loaded sentence that efficiently communicates the tool's scope. Every clause adds information about what is included, with no redundant or filler text.

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 that annotations cover safety, an output schema exists, and parameters are fully documented, the description is largely complete. The main missing element is guidance on how this tool relates to the many sibling tools, which would help an agent select it correctly.

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%, so both parameters (country and locale) are already fully documented. The description does not add any parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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 resource (country) and enumerates the three data components returned: hosted displaced population by category, population displaced from the country, and top origin countries. It is clear what the tool does, but it does not explicitly differentiate itself from siblings like refugee_population, top_host_countries, or generate_country_report.

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?

The phrase 'One-call humanitarian snapshot' implies this tool is useful for a quick overview instead of multiple calls, but there is no explicit guidance on when to use it versus alternatives. With many sibling tools covering overlapping country data, the lack of routing guidance is a notable gap.

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