Malja MCP

Official

by marsaplatform

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Latest statistics

latest_statistics

Read-only

Retrieves current displacement statistics worldwide or for a specific country, letting users compare people hosted versus people displaced by origin in English or Arabic.

Instructions

Most recent displacement figures. With a country: its latest hosted figures. Without: the latest global totals.

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": "latest_statistics"
  }
}

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.
`country`	No	Country name or ISO3; omit for global totals

Output Schema

Name	Required	Description	Default
`year`	Yes
`scope`	Yes
`source`	Yes
`figures`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/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 and the description only needs to add context. It adds the scope split (global vs country) but says nothing about data vintage despite the 'most recent' claim, nor about whether origins data is included. No contradiction with annotations.

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?

Two short sentences, zero filler, with the scope distinction front-loaded in the second sentence. Nothing could be removed without losing routing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value explanation is unnecessary, and the description covers the primary global/country path. The gap is the role parameter: the description frames the output as "hosted figures", which may steer an agent away from role=origin even though the schema supports it. Adequate for the common case, incomplete at the edges.

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 role, locale, and country are all fully documented in the schema. The description reinforces the country/no-country behaviour but adds no syntax or semantics beyond it, and its phrase "hosted figures" actually engages the role parameter only obliquely. Baseline 3 is correct when the schema carries the load.

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 (displacement figures) with an explicit recency qualifier and states the two scoping modes (per-country vs global). It is clear what the tool returns, but it never differentiates itself from near-neighbours like refugee_population, top_host_countries, or country_profile, so an agent must infer the boundary.

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?

"With a country... Without..." does route the caller between two shapes of the same call, which is genuine usage guidance. However, there is no when-to-use-this-vs-that guidance against the many overlapping siblings, and no mention of when the role parameter (asylum vs origin) matters.

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