reliefweb-mcp-server

Search ReliefWeb Disasters

reliefweb_search_disasters

Read-onlyIdempotent

Search active and historical disasters on ReliefWeb by type, country, status, date range, and GLIDE number. Default preset covers alert, ongoing, and past disasters. Use include_archived=true to reach alert-archive entries as well, for historical research. Returns IDs suitable for use with reliefweb_get_disaster and as disaster_id filter in reliefweb_search_reports.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort order. Use date.created:desc for newest first (default), date.created:asc for oldest, score:desc for relevance.
`text`	No	Full-text search query. Matches against disaster name and description.
`glide`	No	GLIDE number (global disaster identifier, e.g., EQ-2023-000053-TUR). Use for cross-system disaster correlation.
`limit`	No	Number of results to return (1–1000, default 10). 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.
`status`	No	Disaster status filter. One of: alert (newly declared), ongoing, past (resolved), alert-archive. Separate multiple values with commas; case, spacing, and punctuation are ignored, and any other value is rejected with the valid list. alert-archive is only reachable with include_archived=true — asking for it without that returns nothing.
`country`	No	ISO 3166-1 alpha-3 country code (e.g., SYR, AFG, UKR). Filters to disasters tagged with this country.
`date_to`	No	Latest disaster creation date. Pair with date_from for a date range. A bare calendar date resolves to end of that day in UTC, so the range covers it in full; a datetime carrying any offset is resolved to UTC.
`date_from`	No	Earliest disaster creation date. Filters on date.created. A bare calendar date such as 2024-01-15 is accepted and resolves to start of that day in UTC; a datetime carrying any offset is resolved to UTC.
`disaster_type`	No	Disaster type name (e.g., Earthquake, Flood, Drought, Cyclone). Filters on type.name.
`include_archived`	No	Include alert-archive disasters in results, alongside alert, ongoing, and past. Uses preset=analysis. Off by default.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`items`	No	Matching disasters.
`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 disasters matching the query before pagination.
`appliedFilters`	No	The resolved filter set the query actually ran with, after normalization and defaults. Echoes back so the agent can confirm how its inputs were interpreted.

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",
+      "appliedFilters",
+      "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: `unknown_status`: A status token does not name a ReliefWeb disaster status. `invalid_query`: ReliefWeb rejected the query — an unrecognized sort field or a malformed date. `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": [
+            "unknown_status",
+            "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",
-  "appliedFilters",
-  "totalCount"
-]

Changed4 schema fields changedAug 7, 2026

changedInput schema / properties / include_archived / description

Previous value: -"Include alert-archive and archive disasters in results. Uses preset=analysis. Off by default."New value: +"Include alert-archive disasters in results, alongside alert, ongoing, and past. Uses preset=analysis. Off by default."

changedInput schema / properties / status / description

Previous value: -"Disaster status filter. Values: alert (newly declared), current (ongoing), past (resolved), alert-archive, archive. Separate multiple values with commas. Default preset includes alert, current, past."New value: +"Disaster status filter. One of: alert (newly declared), ongoing, past (resolved), alert-archive. Separate multiple values with commas; case, spacing, and punctuation are ignored, and any other value is rejected with the valid list. alert-archive is only reachable with include_archived=true — asking for it without that returns nothing."

changedOutput schema / properties / appliedFilters / properties / status / description

Previous value: -"Status filter applied (comma-joined when multiple)."New value: +"Status filter applied, in canonical spelling (comma-joined when multiple)."

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

Previous value: -"Disaster status (alert, current, past, archive)."New value: +"Disaster status: alert, ongoing, past, or alert-archive."

Changed7 schema fields changedAug 7, 2026

addedInput schema / properties / date_from / anyOf

Added value: +[
+  {
+    "const": "",
+    "type": "string"
+  },
+  {
+    "description": "Calendar date (2024-01-15) or full ISO 8601 datetime (2024-01-15T00:00:00+00:00).",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}(?:T\\d{2}:\\d{2}(?::\\d{2}(?:\\.\\d+)?)?(?:Z|[+-]\\d{2}:?\\d{2})?)?$",
+    "type": "string"
+  }
+]

changedInput schema / properties / date_from / description

Previous value: -"Earliest disaster creation date (ISO 8601). Filters on date.created."New value: +"Earliest disaster creation date. Filters on date.created. A bare calendar date such as 2024-01-15 is accepted and resolves to start of that day in UTC; a datetime carrying any offset is resolved to UTC."

removedInput schema / properties / date_from / type
```
Removed value: -"string"
```

addedInput schema / properties / date_to / anyOf

Added value: +[
+  {
+    "const": "",
+    "type": "string"
+  },
+  {
+    "description": "Calendar date (2024-01-31) or full ISO 8601 datetime (2024-01-31T23:59:59+00:00).",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}(?:T\\d{2}:\\d{2}(?::\\d{2}(?:\\.\\d+)?)?(?:Z|[+-]\\d{2}:?\\d{2})?)?$",
+    "type": "string"
+  }
+]

changedInput schema / properties / date_to / description

Previous value: -"Latest disaster creation date (ISO 8601). Pair with date_from for a date range."New value: +"Latest disaster creation date. Pair with date_from for a date range. A bare calendar date resolves to end of that day in UTC, so the range covers it in full; a datetime carrying any offset is resolved to UTC."

removedInput schema / properties / date_to / type
```
Removed value: -"string"
```

changedOutput schema / properties / notice / description

Previous value: -"Recovery hint when results are empty — echoes filters applied and suggests how to broaden."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."

Changed1 schema field changedJul 13, 2026

changedInput schema / properties / country / description

Previous value: -"ISO 3166-1 alpha-3 country code (e.g., SYR, AFG, UKR). Filters to disasters tagged with this primary country."New value: +"ISO 3166-1 alpha-3 country code (e.g., SYR, AFG, UKR). Filters to disasters tagged with this country."

Changed2 schema fields changedJun 16, 2026

addedOutput schema / properties / appliedFilters

Added value: +{
+  "additionalProperties": false,
+  "description": "The resolved filter set the query actually ran with, after normalization and defaults. Echoes back so the agent can confirm how its inputs were interpreted.",
+  "properties": {
+    "country": {
+      "description": "Country code as normalized (uppercased ISO3).",
+      "type": "string"
+    },
+    "dateFrom": {
+      "description": "Earliest creation date filter applied.",
+      "type": "string"
+    },
+    "dateTo": {
+      "description": "Latest creation date filter applied.",
+      "type": "string"
+    },
+    "disasterType": {
+      "description": "Disaster type name filter applied.",
+      "type": "string"
+    },
+    "glide": {
+      "description": "GLIDE number filter applied.",
+      "type": "string"
+    },
+    "limit": {
+      "description": "Result limit the query used.",
+      "type": "number"
+    },
+    "offset": {
+      "description": "Pagination offset the query used.",
+      "type": "number"
+    },
+    "preset": {
+      "description": "ReliefWeb preset the query used: latest (default) or analysis when include_archived.",
+      "type": "string"
+    },
+    "sort": {
+      "description": "Sort order the query used (resolved, including the default).",
+      "type": "string"
+    },
+    "status": {
+      "description": "Status filter applied (comma-joined when multiple).",
+      "type": "string"
+    },
+    "text": {
+      "description": "Full-text query the search used.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "sort",
+    "preset",
+    "limit",
+    "offset"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "items",
-  "totalCount"
-]New value: +[
+  "items",
+  "appliedFilters",
+  "totalCount"
+]

Changed3 schema fields 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."

removedOutput schema / properties / message

Removed value: -{
-  "description": "Recovery hint when results are empty — echoes filters applied and suggests how to broaden.",
-  "type": "string"
-}

addedOutput schema / properties / notice

Added value: +{
+  "description": "Recovery hint when results are empty — echoes filters applied and suggests how to broaden.",
+  "type": "string"
+}

First observedMay 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds significant detail beyond annotations: default preset behavior, archived reachability, quota limit per call (1,000/day), status value validation, and date resolution semantics. The readOnlyHint and idempotentHint are already present, and the description complements them with operational behavior like pagination via totalCount enrichment field.

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, front-loaded with purpose, followed by a critical filtering nuance and a chaining hint. Every sentence earns its place with no redundancy or filler.

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 11-parameter complexity, an output schema for results, and read-only/idempotent annotations, the description covers all essential aspects: defaults, archived behavior, quota, date handling, and downstream usage. An agent has sufficient information to invoke correctly without additional lookups.

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 each parameter's meaning is already documented thoroughly in the schema. The tool description repeats the overall filter categories but does not add new semantic detail beyond what the schema provides. Baseline of 3 is appropriate.

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 clearly states specific verb ('search'), resource ('disasters on ReliefWeb'), and the filter criteria (type, country, status, date range, GLIDE number). It differentiates from sibling tools by mentioning returned IDs suitable for reliefweb_get_disaster and as disaster_id filter in reliefweb_search_reports, establishing its role in a workflow.

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?

Provides clear guidance on when to use include_archived=true for historical research and default preset coverage. Names related siblings for chaining. However, it does not explicitly state when to prefer this search over reliefweb_get_disaster for single-record retrieval, leaving some inference to the agent.

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.