Skip to main content
Glama

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.

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": {
      "id": "<id>"
    },
    "name": "reliefweb_get_disaster"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesReliefWeb numeric disaster ID. Obtained from reliefweb_search_disasters results.
archiveNoArchive 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.
sectionsNoSections 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. Records are sparse, so a name this record does not carry is rejected with the names it does. 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

NameRequiredDescriptionDefault
idNoReliefWeb numeric disaster ID.
kindNofull 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.
nameNoDisaster name.
errorNoPresent when the call failed. Absent on success.
glideNoGLIDE number for cross-system correlation.
typesNoDisaster type names.
noticeNoRequested and applied archive limits when the page size was clamped.
statusNoDisaster status: alert, ongoing, past, or alert-archive.
archiveNoOne page of a curated list's archived entries, returned in place of the record.
sectionsNoEvery section of the record, largest first. Pass the names back in `sections` to retrieve them.
urlAliasNoCanonical ReliefWeb URL for this disaster.
countriesNoAll countries tagged on this disaster.
dateEventNoEvent date (ISO 8601), when available.
keyContentNoCurrently-active curated key content links from the ReliefWeb editorial team — the present curated set. The archived entries are reachable with archive: { list: "keyContent" }.
dateCreatedNoReliefWeb index date (ISO 8601).
descriptionNoFull disaster description text.
primaryTypeNoPrimary disaster type.
usefulLinksNoCurrently-active useful external links curated by ReliefWeb editors — the present set. The archived entries are reachable with archive: { list: "usefulLinks" }.
outlineNoticeNoHow to re-call this tool for specific sections of the record.
primaryCountryNoPrimary affected country.
profileOverviewNoProfile overview text from the ReliefWeb editorial team.
appealsResponsePlansNoCurrently-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.

  1. Changed3 schema fields changed
    • changedInput schema / properties / archive / properties / limit / description
      Previous value: -"Maximum archived entries in one page (1-100)."New value: +"Maximum archived entries in one page (1-100). Larger integers are clamped with a notice when clamping is enabled; otherwise they are rejected."
    • changedInput schema / properties / archive / properties / limit / maximum
      Previous value: -100New value: +9007199254740991
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Requested and applied archive limits when the page size was clamped.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / sections / description
      Previous value: -"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."New value: +"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. Records are sparse, so a name this record does not carry is rejected with the names it does. 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."
  3. Changed6 schema fields changed
    • 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"
      -]
  4. Changed10 schema fields changed
    • 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"
      +]
  5. Changed1 schema field changed
    • changedOutput schema / properties / status / description
      Previous value: -"Disaster status (alert, current, past, archive)."New value: +"Disaster status: alert, ongoing, past, or alert-archive."
  6. Changed3 schema fields changed
    • 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."
  7. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With readOnly/idempotent/openWorld already annotated, the description adds substantial non-obvious behavior: prose can run to tens of KB, oversized records return a section outline with byte sizes, nothing is truncated on any path, and sparse records reject unknown section names with the valid names. Archive mode's page semantics (bounded by limit, never outlines) are also disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the call-order hint, then behavior, then sizing caveats. Dense but each clause carries information; only "Nothing is truncated on any path" mildly repeats the outline/budget sentences.

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?

An output schema exists, so return values need not be explained, yet the description still covers the tricky paths (outline response, archive paging, identity metadata always included). Nothing an agent needs to invoke this correctly 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 description coverage is 100%, so the baseline is 3 — the schema already documents id, sections, and the archive object in depth. The description restates the selector exclusivity and the outline-named sections convention, which is helpful framing but largely duplicative of what the schema already spells out.

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?

States a specific verb and resource ("Fetch a disaster record by ReliefWeb numeric ID") and enumerates the payload (description, affected countries, GLIDE number, profile overview, key content links, appeals). It also names the sibling it complements (reliefweb_search_disasters), so an agent can distinguish it from the search tools without opening a schema.

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 routes the agent: "Use after reliefweb_search_disasters to retrieve full details." It also states a constraint the agent must respect (two alternative selectors, at most one per call) and which selector wins for archived entries versus record sections.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.