reliefweb-mcp-server

Get ReliefWeb Country Profile

reliefweb_get_country

Read-onlyIdempotent

Fetch a country profile from ReliefWeb by ISO3 code, including overview, humanitarian situation summary, key content links, active appeals and response plans, and useful external links. Country profiles are curated by OCHA editors and provide the authoritative situation summary for humanitarian responders. Each curated list also has an archive — thousands of entries deep for a long-running crisis — which the profile leaves out. Two alternative selectors, at most one per call: sections names parts of the profile to return, archive pages one list's archived entries in place of the profile. A profile 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

Name	Required	Description
`iso3`	Yes	ISO 3166-1 alpha-3 country code (e.g., SYR, AFG, UKR). Used to look up the country's ReliefWeb profile.
`archive`	No	Archive mode: return a page of one curated list's ARCHIVED entries instead of the country 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 country 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 profile itself and never reaches archived entries — use archive for those.

Output Schema

Name	Required	Description
`id`	No	ReliefWeb numeric country ID.
`iso3`	No	ISO 3166-1 alpha-3 code.
`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	Country name.
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Requested and applied archive limits when the page size was clamped.
`status`	No	Humanitarian situation status.
`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 country page.
`keyContent`	No	Currently-active curated key content links maintained by ReliefWeb editors — the present curated set. The archived entries are reachable with archive: { list: "keyContent" }.
`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.
`profileOverview`	No	Situation overview text from the ReliefWeb editorial team.
`appealsResponsePlans`	No	Currently-active humanitarian appeals and response plans for this country — the present set. The archived entries are reachable with archive: { list: "appealsResponsePlans" }.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

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"
+}

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / sections / description

Previous value: -"Sections of the country 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 profile itself and never reaches archived entries — use archive for those."New value: +"Sections of the country 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 profile itself and never reaches archived entries — use archive for those."

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 country profile found for the given ISO3 code. `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 country 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 country 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 profile 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 humanitarian appeals and response plans for this country — the present set, not the full historical archive."New value: +"Currently-active humanitarian appeals and response plans for this country — 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 maintained by ReliefWeb editors — the present curated set, not the full historical archive."New value: +"Currently-active curated key content links maintained by ReliefWeb editors — 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"
+]

Changed3 schema fields changedJul 13, 2026

changedOutput schema / properties / appealsResponsePlans / description

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

changedOutput schema / properties / keyContent / description

Previous value: -"Curated key content links maintained by ReliefWeb editors."New value: +"Currently-active curated key content links maintained by ReliefWeb editors — 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.6/5.0

Behavior5/5

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

Annotations already mark this read-only and idempotent, and the description adds context they cannot carry: over-budget records come back as a section outline with per-section byte sizes, nothing is truncated, archive calls still answer regardless of record size, and mutually-exclusive selectors are rejected. That is precisely the kind of operational detail an agent needs before calling.

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, then selectors, then the budget/outline behavior — a sensible order with no padding sentences. The archive aside ('thousands of entries deep for a long-running crisis') is mildly rhetorical but justifies why archive mode exists, so it still earns its place.

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?

For a three-parameter tool with nested objects and a full output schema, the description covers everything the structured fields don't: selector exclusivity, outline-on-oversize behavior, sparse-section rejection, and non-truncation guarantees. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3; the description earns above that by explaining what a section name must match (an outline's spelling), that a missing name is rejected with the names the record does carry, and that identity metadata returns alongside any slice. It doesn't restate limit/offset paging semantics, which the schema already handles.

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 country profile from ReliefWeb by ISO3 code') and enumerates the contents the profile returns. The selector semantics (sections vs archive) are named up front, so an agent can separate this from reliefweb_list_countries or reliefweb_search_reports without reading the schema.

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?

Explicitly frames 'sections' and 'archive' as two alternative selectors, 'at most one per call', and states that archive reaches the entries the profile leaves out — a real when-to-use rule. It doesn't route the agent to siblings for discovering an ISO3 code (reliefweb_list_countries) or for full-text retrieval, so removal of exclusions keeps it below a 5.

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.