reliefweb-mcp-server

List ReliefWeb Sources

reliefweb_list_sources

Read-onlyIdempotent

Browse source organizations that contribute content to ReliefWeb, optionally filtered by name text or organization type. Returns short names, types, and URLs. Use the shortname value with the source filter in reliefweb_search_reports, reliefweb_search_jobs, and reliefweb_search_training.

Input Schema

TableJSON Schema

Name	Required	Description
`text`	No	Full-text search query. Matches against organization name and short name.
`type`	No	Organization type. One of: Non-governmental Organization, International Organization, Academic and Research Institution, Other, Government, Media, Red Cross/Red Crescent Movement. Filters on type.name.
`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.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`items`	No	Source organizations contributing content to ReliefWeb.
`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 sources matching the query before pagination.

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",
+      "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: `invalid_query`: ReliefWeb rejected the request as malformed rather than failing to serve it. `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": [
+            "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",
-  "totalCount"
-]

Changed1 schema field changedAug 7, 2026

changedOutput schema / properties / notice / description

Previous value: -"Recovery hint when results are empty — echoes the active filters and suggests how to broaden. Absent on successful result pages."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."

Changed2 schema fields changedJul 13, 2026

changedInput schema / properties / type / description

Previous value: -"Organization type. Must match exact API values: \"Government\", \"International Organization\", \"Non-governmental Organization\", \"Academia\", \"United Nations\", \"Other\". Filters on type.name."New value: +"Organization type. One of: Non-governmental Organization, International Organization, Academic and Research Institution, Other, Government, Media, Red Cross/Red Crescent Movement. Filters on type.name."

addedInput schema / properties / type / enum

Added value: +[
+  "Non-governmental Organization",
+  "International Organization",
+  "Academic and Research Institution",
+  "Other",
+  "Government",
+  "Media",
+  "Red Cross/Red Crescent Movement"
+]

Changed1 schema field changedJun 16, 2026

addedOutput schema / properties / notice

Added value: +{
+  "description": "Recovery hint when results are empty — echoes the active filters and suggests how to broaden. Absent on successful result pages.",
+  "type": "string"
+}

Changed1 schema field changedJun 4, 2026

changedInput schema / properties / type / description

Previous value: -"Organization type (e.g., Government, International Organization, NGO, Academia). Filters on type.name."New value: +"Organization type. Must match exact API values: \"Government\", \"International Organization\", \"Non-governmental Organization\", \"Academia\", \"United Nations\", \"Other\". Filters on type.name."

Changed1 schema field 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."

First observedMay 29, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already disclose readOnlyHint, openWorldHint, and idempotentHint, so the safety and repeatability profile is covered. The description adds only that it returns short names, types, and URLs, which is minor and does not go beyond what the output schema would convey. No contradiction with annotations.

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 two sentences long, with the core purpose front-loaded and the downstream usage in the second sentence. There is no filler or redundancy; every sentence 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 simple list tool with four optional parameters, all documented in the schema, and an output schema present, the description covers the essential context: what it lists, optional filters, returned fields, and how to use the output. It also leaves pagination details to the parameter descriptions, which is appropriate.

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 each parameter (text, type, limit, offset) is fully documented in the schema. The tool description only restates the option to filter by name text or organization type, adding no new meaning beyond the schema. This matches the baseline for full schema coverage.

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 ('browse') and resource ('source organizations'), and explicitly lists the returned fields (short names, types, URLs). It is clearly distinct from sibling tools like reliefweb_list_countries, which lists countries rather than sources.

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?

The description gives concrete downstream guidance: use the returned shortname value with the source filter in the search tools. It does not explicitly state when to use this tool versus alternatives, but the resource type is unambiguous relative to sibling list_countries, so the usage context is clear enough.

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.