reliefweb-mcp-server

Get ReliefWeb Disaster

reliefweb_get_disaster

Read-onlyIdempotent

Fetch a disaster record by ReliefWeb numeric ID including description, affected countries, GLIDE number, profile overview, key content links, and active appeals or response plans. Use after reliefweb_search_disasters to retrieve full details. Each curated list also has an archive, which the record leaves out. Two alternative selectors, at most one per call: sections names parts of the record to return, archive pages one list's archived entries in place of the record. Description and profile overview can together run to tens of KB for major disasters. A record over the response budget comes back as a section outline naming every section and its byte size. Nothing is truncated on any path.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	ReliefWeb numeric disaster ID. Obtained from reliefweb_search_disasters results.
`archive`	No	Archive mode: return a page of one curated list's ARCHIVED entries instead of the disaster record. The response carries the record identity, the selected list, and total / shown / offset, plus a next offset while more entries remain. Mutually exclusive with sections — sections slices the record, archive replaces it — and a call supplying both is rejected. A record over the response budget still answers an archive call with the page: a page is bounded by limit and carries none of the record prose, so it never outlines.
`sections`	No	Sections of the disaster record to return, named by the sections[].name values an outline response lists. Omit for the whole record, or for a section outline when the record is over the response budget. Identity metadata — the record's ID, its name, and its canonical URL — comes back alongside whatever is requested. The call is self-contained — the record is re-fetched and sliced, so no prior call has to be repeated. This names parts of the record itself and never reaches archived entries — use archive for those.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	ReliefWeb numeric disaster ID.
`kind`	No	full when the record — or the sections asked for — is returned in whole; outline when the record exceeded the response budget and only its section index is returned; archive when the call asked for a page of one curated list's archived entries, which is returned in place of the record.
`name`	No	Disaster name.
`error`	No	Present when the call failed. Absent on success.
`glide`	No	GLIDE number for cross-system correlation.
`types`	No	Disaster type names.
`status`	No	Disaster status: alert, ongoing, past, or alert-archive.
`archive`	No	One page of a curated list's archived entries, returned in place of the record.
`sections`	No	Every section of the record, largest first. Pass the names back in `sections` to retrieve them.
`urlAlias`	No	Canonical ReliefWeb URL for this disaster.
`countries`	No	All countries tagged on this disaster.
`dateEvent`	No	Event date (ISO 8601), when available.
`keyContent`	No	Currently-active curated key content links from the ReliefWeb editorial team — the present curated set. The archived entries are reachable with archive: { list: "keyContent" }.
`dateCreated`	No	ReliefWeb index date (ISO 8601).
`description`	No	Full disaster description text.
`primaryType`	No	Primary disaster type.
`usefulLinks`	No	Currently-active useful external links curated by ReliefWeb editors — the present set. The archived entries are reachable with archive: { list: "usefulLinks" }.
`outlineNotice`	No	How to re-call this tool for specific sections of the record.
`primaryCountry`	No	Primary affected country.
`profileOverview`	No	Profile overview text from the ReliefWeb editorial team.
`appealsResponsePlans`	No	Currently-active appeals and response plans linked to this disaster — the present set. The archived entries are reachable with archive: { list: "appealsResponsePlans" }.

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": [
+      "kind"
+    ]
+  },
+  {
+    "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: `not_found`: No disaster found with the given ID. `selector_conflict`: The call supplied both sections and archive, which select different things. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "selector_conflict"
+          ],
+          "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: -[
-  "kind"
-]
```

Changed10 schema fields changedAug 7, 2026

addedInput schema / properties / archive

Added value: +{
+  "description": "Archive mode: return a page of one curated list's ARCHIVED entries instead of the disaster record. The response carries the record identity, the selected list, and total / shown / offset, plus a next offset while more entries remain. Mutually exclusive with sections — sections slices the record, archive replaces it — and a call supplying both is rejected. A record over the response budget still answers an archive call with the page: a page is bounded by limit and carries none of the record prose, so it never outlines.",
+  "properties": {
+    "limit": {
+      "default": 25,
+      "description": "Maximum archived entries in one page (1-100).",
+      "maximum": 100,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "list": {
+      "description": "Which curated list to page. The archived entries of that list are the ones the profile itself leaves out.",
+      "enum": [
+        "keyContent",
+        "appealsResponsePlans",
+        "usefulLinks"
+      ],
+      "type": "string"
+    },
+    "offset": {
+      "default": 0,
+      "description": "Zero-based index of the first archived entry to return. Send back the nextOffset from the previous page to continue.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "list"
+  ],
+  "type": "object"
+}

addedInput schema / properties / sections

Added value: +{
+  "description": "Sections of the disaster record to return, named by the sections[].name values an outline response lists. Omit for the whole record, or for a section outline when the record is over the response budget. Identity metadata — the record's ID, its name, and its canonical URL — comes back alongside whatever is requested. The call is self-contained — the record is re-fetched and sliced, so no prior call has to be repeated. This names parts of the record itself and never reaches archived entries — use archive for those.",
+  "items": {
+    "description": "A section name exactly as the outline response spelled it.",
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / appealsResponsePlans / description

Previous value: -"Currently-active appeals and response plans linked to this disaster — the present set, not the full historical archive."New value: +"Currently-active appeals and response plans linked to this disaster — the present set. The archived entries are reachable with archive: { list: \"appealsResponsePlans\" }."

addedOutput schema / properties / archive

Added value: +{
+  "additionalProperties": false,
+  "description": "One page of a curated list's archived entries, returned in place of the record.",
+  "properties": {
+    "entries": {
+      "description": "The archived entries in this page, in ReliefWeb's own archive order.",
+      "items": {
+        "additionalProperties": false,
+        "description": "One archived entry.",
+        "properties": {
+          "date": {
+            "description": "Publication date, carried by appeals and response plans.",
+            "type": "string"
+          },
+          "title": {
+            "description": "Entry title.",
+            "type": "string"
+          },
+          "url": {
+            "description": "Entry URL.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "list": {
+      "description": "The curated list this page was read from.",
+      "enum": [
+        "keyContent",
+        "appealsResponsePlans",
+        "usefulLinks"
+      ],
+      "type": "string"
+    },
+    "nextOffset": {
+      "description": "Offset to send back to read the next page. Absent when this page reaches the end of the archive.",
+      "type": "number"
+    },
+    "offset": {
+      "description": "Zero-based index of the first entry in this page.",
+      "type": "number"
+    },
+    "shown": {
+      "description": "Number of entries in this page.",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total archived entries in that list for this record.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "list",
+    "total",
+    "shown",
+    "offset",
+    "entries"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / keyContent / description

Previous value: -"Currently-active curated key content links from the ReliefWeb editorial team — the present curated set, not the full historical archive."New value: +"Currently-active curated key content links from the ReliefWeb editorial team — the present curated set. The archived entries are reachable with archive: { list: \"keyContent\" }."

addedOutput schema / properties / kind

Added value: +{
+  "description": "full when the record — or the sections asked for — is returned in whole; outline when the record exceeded the response budget and only its section index is returned; archive when the call asked for a page of one curated list's archived entries, which is returned in place of the record.",
+  "enum": [
+    "full",
+    "outline",
+    "archive"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / outlineNotice

Added value: +{
+  "description": "How to re-call this tool for specific sections of the record.",
+  "type": "string"
+}

addedOutput schema / properties / sections

Added value: +{
+  "description": "Every section of the record, largest first. Pass the names back in `sections` to retrieve them.",
+  "items": {
+    "additionalProperties": false,
+    "description": "One retrievable section of the record: its name and its serialized size.",
+    "properties": {
+      "bytes": {
+        "description": "Serialized byte size of the section",
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "name": {
+        "description": "Section identifier — pass in `sections` to retrieve it",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "bytes"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / usefulLinks / description

Previous value: -"Currently-active useful external links curated by ReliefWeb editors — the present set, not the full historical archive."New value: +"Currently-active useful external links curated by ReliefWeb editors — the present set. The archived entries are reachable with archive: { list: \"usefulLinks\" }."

changedOutput schema / required

Previous value: -[
-  "id",
-  "name"
-]New value: +[
+  "kind"
+]

Changed1 schema field changedAug 7, 2026

changedOutput schema / properties / status / description

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

Changed3 schema fields changedJul 13, 2026

changedOutput schema / properties / appealsResponsePlans / description

Previous value: -"Active appeals and response plans linked to this disaster."New value: +"Currently-active appeals and response plans linked to this disaster — the present set, not the full historical archive."

changedOutput schema / properties / keyContent / description

Previous value: -"Curated key content links from the ReliefWeb editorial team."New value: +"Currently-active curated key content links from the ReliefWeb editorial team — the present curated set, not the full historical archive."

changedOutput schema / properties / usefulLinks / description

Previous value: -"Useful external links curated by ReliefWeb editors."New value: +"Currently-active useful external links curated by ReliefWeb editors — the present set, not the full historical archive."

First observedMay 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, covering safety and idempotency. The description goes well beyond by disclosing the size risk ('Description and profile overview can together run to tens of KB'), the outline fallback when over budget, the guarantee that 'Nothing is truncated on any path,' and the archive mode's pagination semantics. This provides rich behavioral context that annotations cannot express.

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?

The description is dense but every sentence earns its place. It front-loads the primary purpose, then explains usage context, then details the selectors and edge cases. The structure is clear: main fetch, then two alternative modes, then size behavior. No filler or redundancy; it is long only because it packs precise, non-repeating information.

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 tool's complexity (two selectors, pagination, outline fallback, size constraints), the description covers all necessary operational aspects. It explains the archive page response structure (identity, list, total/shown/offset, next offset), the sections requirement of exact names from the outline, and the self-contained nature of calls. An output schema exists, so return-value details are not needed; the description fully equips an agent to invoke the tool correctly in all documented scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter (id, archive, sections) is already documented with types, defaults, and descriptions. The description adds critical meaning beyond the schema: it explains the mutual exclusivity of archive and sections, the exact behavior of each selector (archive replaces the record, sections slices it), and how the outline response supplies section names for the sections parameter. This is more than the baseline 3, though the schema already carries heavy weight.

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 ('Fetch') and resource ('disaster record by ReliefWeb numeric ID') and enumerates the returned content (description, affected countries, GLIDE number, profile overview, key content links, active appeals/response plans). It clearly differentiates from sibling search tools by prescribing use after reliefweb_search_disasters and by introducing the archive selector, which is unique to this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly directs 'Use after reliefweb_search_disasters to retrieve full details.' It further explains when to use the archive parameter (to retrieve archived entries not in the record) and when the sections parameter is needed (to target specific parts or handle oversized records). It also states that a record over the budget returns a section outline, giving a clear contingency path. No alternative tool is named, but the usage context is unambiguous.

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.