Skip to main content
Glama

reliefweb-mcp-server

by io.github.cyanheads

Search ReliefWeb Training

reliefweb_search_training
Read-onlyIdempotent

Search humanitarian training and learning opportunities on ReliefWeb by country, format, date, source, career category, and language. Covers on-site and online capacity-building events. Training date fields use date.start / date.end — different from report date fields. Use date_start_from and date_start_to to find upcoming training within a window. Results default to soonest-starting first (date.start:asc). With neither date bound supplied the search is scoped to training starting from now, so the first page is upcoming opportunities; supply either bound to search an explicit range, including a historical one. Use include_archived=true to search concluded listings as well, which are far more numerous than the current ones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order. Use date.start:asc for soonest-starting training first (default), date.start:desc for latest-starting, date.created:desc for most recently posted, or score:desc for relevance.
textNoFull-text search query. Matches against training title and description.
limitNoNumber of results to return (1–1000, default 10). Each call counts against the 1,000-calls/day quota.
formatNoTraining format. Valid values: on-site, online. Filters on format.name.
offsetNoZero-based offset for pagination. Use with limit and the totalCount enrichment field to page through results.
sourceNoOrganization short name. Filters on source.shortname.
countryNoISO 3166-1 alpha-3 country code (e.g., KEN, ETH, COD). Filters to training tagged with this country.
languageNoISO 639-1 language code (e.g., en, fr, es). Filters on language.code.
date_start_toNoTraining start date upper bound. Filters on date.start — pair with date_start_from for a window. A bare calendar date resolves to end of that day in UTC, and a datetime carrying any offset is resolved to UTC. Supplying this alone searches everything up to it, with no lower bound injected.
career_categoryNoHumanitarian career track (e.g., Programme and Project Management, Information and Communications Technology). Filters on career_categories.name.
date_start_fromNoTraining start date lower bound. Filters on date.start — use to find training starting after a given date. A bare calendar date resolves to start of that day in UTC, and a datetime carrying any offset is resolved to UTC. Omit this and date_start_to together to default the search to training starting from now, unless include_archived is set, which leaves the range open.
include_archivedNoSearch concluded listings alongside the current ones. Uses preset=analysis. Off by default. Setting this also drops the start-from-now default bound, so an otherwise unbounded search reaches back through the whole record; pair it with date_start_from and date_start_to to study a specific period.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
itemsNoMatching training opportunities.
noticeNoPresent 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.
totalCountNoTotal training listings matching the query before pagination.
appliedFiltersNoThe resolved filter set the query actually ran with, after normalization and defaults. Echoes back so the agent can confirm how its inputs were interpreted.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description reveals default sorting (date.start:asc), the implicit date scoping when no bounds are supplied, the effect of include_archived on the range, and warns that training date fields are different from report date fields. These behavioral details are not present in the annotations or schema, adding substantial value.

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 a single, compact paragraph with no fluff. It front-loads the purpose, then packs key behavioral rules (date field difference, sorting, default scoping, archived inclusion) into a few sentences. Every sentence contributes distinctive information, achieving high information density without being verbose.

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 12 parameters, 100% schema coverage, and an existing output schema, the description concentrates on the non-obvious aspects: default date range behavior, sorting defaults, and the archived toggle. It also flags the field naming difference from other tools. No critical operational ambiguity remains that would prevent an agent from calling it correctly.

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?

The schema already provides 100% coverage with rich descriptions for each parameter. The description adds meaningful interaction semantics: how date_start_from/date_start_to work together to define a window, the default behavior when both are omitted, and the consequence of include_archived on the range. This goes beyond the schema's individual parameter explanations.

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 clearly states 'Search humanitarian training and learning opportunities' with specific filters (country, format, date, source, career category, language). It distinguishes this from sibling search tools (reports, jobs) by explicitly focusing on 'training', and clarifies it covers on-site and online capacity-building events. This is a specific verb + resource with clear scope.

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?

Provides explicit guidance on using date bounds for windows, the default start-from-now behavior, and when to use include_archived. It notes that training date fields differ from report date fields, which is a subtle usage hint. However, it doesn't explicitly name alternative sibling tools for non-training queries, so it stops short of a full 'when-not-to-use' statement.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct resource type (country, disaster, job, report, training, source) and a clear action (get, list, search). The search/get pairs are clearly separated by resource, with no overlapping purposes.

Naming Consistency5/5

All tools follow the consistent pattern reliefweb_<verb>_<noun>, using get, list, and search as verbs. The only minor variation is list_countries vs list_sources, but the plural nouns are appropriate for list operations.

Tool Count5/5

11 tools is well within the ideal range and covers five content types plus country and source lookups. Each tool serves a distinct function, making the set comprehensive without being bloated.

Completeness5/5

The surface provides both search and fetch operations for all primary resources (disasters, jobs, reports, training) and complete country/source lookup coverage. No obvious gaps for a read-only humanitarian data API.

Resources