reliefweb-mcp-server

List ReliefWeb Countries

reliefweb_list_countries

Read-onlyIdempotent

List all countries and territories tracked by ReliefWeb, optionally filtered to active humanitarian situations. Returns ISO3 codes and status for each entry — use the ISO3 code with reliefweb_get_country to fetch a full profile. Set crisis_only=true to limit results to countries with active humanitarian situations.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of results to return (1–1000, default 100). Each call counts against the 1,000-calls/day quota.
`offset`	No	Zero-based offset for pagination. Use with limit and the totalCount enrichment field to page through results.
`crisis_only`	No	When true, filters to countries with an active humanitarian situation (status ongoing). Default false returns all countries.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`items`	No	Countries tracked by ReliefWeb.
`notice`	No	Present only when the page is empty. Names the match count and the last reachable offset when the query matched records; otherwise echoes the filters applied and suggests how to broaden.
`totalCount`	No	Total countries matching the filter before pagination.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "items",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_query`: ReliefWeb rejected the request as malformed rather than failing to serve it. `upstream_error`: The ReliefWeb API was unreachable, timed out, or returned a server error. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_query",
+            "upstream_error"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "items",
-  "totalCount"
-]

Changed1 schema field changedAug 7, 2026

changedOutput schema / properties / notice / description

Previous value: -"Recovery hint when results are empty — echoes the active filter and suggests how to broaden. Absent on successful result pages."New value: +"Present only when the page is empty. Names the match count and the last reachable offset when the query matched records; otherwise echoes the filters applied and suggests how to broaden."

Changed2 schema fields changedJul 13, 2026

changedInput schema / properties / crisis_only / description

Previous value: -"When true, filters to countries with an active humanitarian situation (status alert or current). Default false returns all countries."New value: +"When true, filters to countries with an active humanitarian situation (status ongoing). Default false returns all countries."

changedOutput schema / properties / items / items / properties / status / description

Previous value: -"Humanitarian situation status. Active situations have status alert or current."New value: +"Humanitarian situation status: ongoing (active crisis) or normal (non-crisis)."

Changed1 schema field changedJun 16, 2026

addedOutput schema / properties / notice

Added value: +{
+  "description": "Recovery hint when results are empty — echoes the active filter and suggests how to broaden. Absent on successful result pages.",
+  "type": "string"
+}

Changed1 schema field changedMay 30, 2026

changedInput schema / properties / offset / description

Previous value: -"Zero-based offset for pagination. Use with limit and totalCount to page through results."New value: +"Zero-based offset for pagination. Use with limit and the totalCount enrichment field to page through results."

First observedMay 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnly, openWorld, and idempotent hints. The description adds valuable behavioral context by stating what is returned (ISO3 codes and status) and how the optional filter affects results ('crisis_only=true to limit results to countries with active humanitarian situations'). This goes beyond the annotations without contradicting them.

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 sentences with no filler. The core function and output are front-loaded, followed by the filter usage and a pointer to the sibling. Every word contributes value.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and annotations cover safety, the description is sufficient. It mentions the key output fields, the optional filter, and points to the sibling for full details. The pagination and rate limit are already in the schema, so nothing critical is missing.

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% with detailed descriptions for limit, offset, and crisis_only, so the description adds little beyond reminding the agent to use crisis_only. The baseline is 3 because the schema carries the parameter semantics; the description does not introduce new meaning beyond the schema.

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?

The description states a specific verb ('List') and resource ('all countries and territories tracked by ReliefWeb'), distinguishes from the sibling reliefweb_get_country by noting it returns a list, and clarifies the optional crisis filter. This clearly differentiates it from the other list/search tools.

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?

The description provides an explicit alternative: 'use the ISO3 code with reliefweb_get_country to fetch a full profile.' It also gives a usage condition for crisis_only. However, it does not explicitly state when NOT to use this tool compared to the search tools (e.g., when a country-specific query is needed), but the given guidance is sufficient for the main alternative.

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

All reliefweb-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.