reliefweb-mcp-server

Get ReliefWeb Report

reliefweb_get_report

Read-onlyIdempotent

Fetch a single ReliefWeb report by its numeric ID with full body text, file attachments, and all metadata. Use after reliefweb_search_reports to retrieve document content — body is excluded from search results to manage context budget. Report bodies can be 10–100KB. A record over the response budget comes back as a section outline naming every section and its byte size; re-call with sections to pull only the ones needed. Nothing is truncated on either path.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	ReliefWeb numeric report ID. Obtained from reliefweb_search_reports results.
`sections`	No	Sections of the report 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.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	ReliefWeb numeric report ID.
`body`	No	Full report body text (HTML). Present for most reports; absent for binary-only documents.
`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.
`error`	No	Present when the call failed. Absent on success.
`title`	No	Report title.
`themes`	No	Humanitarian theme/sector names.
`formats`	No	Content format names.
`sources`	No	Publishing organizations (short names).
`fileUrls`	No	Direct file download URLs attached to this report.
`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 report.
`countries`	No	All countries tagged on this report.
`languages`	No	Language codes (ISO 639-1).
`dateCreated`	No	ReliefWeb index date (ISO 8601).
`dateOriginal`	No	Source publication date (ISO 8601).
`outlineNotice`	No	How to re-call this tool for specific sections of the record.
`primaryCountry`	No	Primary country name for this report.
`headlineSummary`	No	Short editorial summary from the headline block, when present.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / sections / description

Previous value: -"Sections of the report 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."New value: +"Sections of the report 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."

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 report found with the given ID. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found"
+          ],
+          "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"
-]
```

Changed5 schema fields changedAug 7, 2026

addedInput schema / properties / sections

Added value: +{
+  "description": "Sections of the report 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.",
+  "items": {
+    "description": "A section name exactly as the outline response spelled it.",
+    "type": "string"
+  },
+  "type": "array"
+}

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.",
+  "enum": [
+    "full",
+    "outline"
+  ],
+  "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 / required

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

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 cover readOnly/idempotent/openWorld, but the description adds substantial behavioral context beyond them: body sizes of 10–100KB, the response-budget outline fallback, the re-call-with-sections pattern, and the explicit 'nothing is truncated on either path' guarantee.

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?

Front-loaded with the core purpose, then the workflow (search first), then the budget/fallback mechanics. Dense but every sentence carries distinct information with no 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?

An output schema exists, yet the description still adequately covers the two response paths and the size/outline behavior. Nothing an agent needs to call and interpret this tool 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, but the description adds real meaning: sections must match outline-spelled names, sparse records cause rejection with the valid names listed, and identity metadata is always returned alongside requested sections. This goes beyond the schema's own text.

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 (fetch) and resource (single ReliefWeb report by numeric ID) plus the payload returned (body text, attachments, metadata). This clearly distinguishes it from reliefweb_search_reports and the other get_* siblings.

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 says to use it after reliefweb_search_reports to retrieve document content, and explains why (bodies excluded from search results to manage context budget). It also names the alternative path (re-call with sections) for oversized records.

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.