Skip to main content
Glama

Search ReliefWeb Training

reliefweb_search_training
Read-onlyIdempotent

Search humanitarian training and learning opportunities on ReliefWeb by country, format, date, source, career category, cost, listing language, and delivery 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reliefweb_search_training"
  }
}

Input Schema

NameRequiredDescriptionDefault
costNoTraining cost: free or fee-based. Case, spacing, and punctuation are ignored; blank is omitted.
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). Larger integers are clamped to 1000 with a notice when clamping is enabled; otherwise they are rejected. 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.
languageNoListing language code (ISO 639-1, e.g., en, fr, es). Filters on language.code; use training_language for the course delivery language.
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_categoryNoReliefWeb career-category name (e.g., Program/Project Management, Information and Communications Technology, Logistics/Procurement). 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.
training_languageNoCourse delivery language code (ISO 639-1, e.g., en, fr, es). Filters on training_language.code independently of the listing language.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
itemsNoMatching training opportunities.
noticeNoDiscloses requested and applied limits when clamped. For empty pages, names the match count and last reachable offset when records matched; otherwise echoes filters 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • changedInput schema / properties / career_category / description
      Previous value: -"Humanitarian career track (e.g., Programme and Project Management, Information and Communications Technology). Filters on career_categories.name."New value: +"ReliefWeb career-category name (e.g., Program/Project Management, Information and Communications Technology, Logistics/Procurement). Filters on career_categories.name."
    • addedInput schema / properties / cost
      Added value: +{
      +  "description": "Training cost: free or fee-based. Case, spacing, and punctuation are ignored; blank is omitted.",
      +  "type": "string"
      +}
    • changedInput schema / properties / language / description
      Previous value: -"ISO 639-1 language code (e.g., en, fr, es). Filters on language.code."New value: +"Listing language code (ISO 639-1, e.g., en, fr, es). Filters on language.code; use training_language for the course delivery language."
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results to return (1–1000, default 10). Each call counts against the 1,000-calls/day quota."New value: +"Number of results to return (1–1000, default 10). Larger integers are clamped to 1000 with a notice when clamping is enabled; otherwise they are rejected. Each call counts against the 1,000-calls/day quota."
    • changedInput schema / properties / limit / maximum
      Previous value: -1000New value: +9007199254740991
    • addedInput schema / properties / training_language
      Added value: +{
      +  "description": "Course delivery language code (ISO 639-1, e.g., en, fr, es). Filters on training_language.code independently of the listing language.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / appliedFilters / properties / cost
      Added value: +{
      +  "description": "Canonical training cost filter applied.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / appliedFilters / properties / language / description
      Previous value: -"Language code filter applied."New value: +"Listing language code filter applied."
    • addedOutput schema / properties / appliedFilters / properties / trainingLanguage
      Added value: +{
      +  "description": "Course delivery language code filter applied.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_query`: ReliefWeb rejected the query — an unrecognized sort field or a malformed date. `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."New value: +"Machine-readable failure mode. Declared by this tool: `unknown_cost`: The cost value does not name a ReliefWeb training cost category. `invalid_date`: A date bound contains impossible calendar or time components. `invalid_query`: ReliefWeb rejected the query — possible causes include malformed text, an unrecognized sort field, or a malformed date. `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."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "invalid_query",
      -  "upstream_error"
      -]New value: +[
      +  "unknown_cost",
      +  "invalid_date",
      +  "invalid_query",
      +  "upstream_error"
      +]
    • addedOutput schema / properties / items / items / properties / cost
      Added value: +{
      +  "description": "Training cost category when supplied by the listing.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / items / items / properties / languages / description
      Previous value: -"Language codes (ISO 639-1)."New value: +"Listing language codes (ISO 639-1)."
    • addedOutput schema / properties / items / items / properties / trainingLanguages
      Added value: +{
      +  "description": "Course delivery language codes (ISO 639-1).",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / notice / description
      Previous 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."New value: +"Discloses requested and applied limits when clamped. For empty pages, names the match count and last reachable offset when records matched; otherwise echoes filters and suggests how to broaden."
  2. 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": [
      +      "items",
      +      "appliedFilters",
      +      "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 query — an unrecognized sort field or a malformed date. `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",
      -  "appliedFilters",
      -  "totalCount"
      -]
  3. Changed5 schema fields changed
    • changedInput schema / properties / date_start_from / description
      Previous value: -"Training 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."New value: +"Training 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."
    • addedInput schema / properties / include_archived
      Added value: +{
      +  "description": "Search 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.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / appliedFilters / properties / dateStartFrom / description
      Previous value: -"Training start date lower bound applied — the caller-supplied value, or the current timestamp when neither date bound was given."New value: +"Training start date lower bound applied — the caller-supplied value, or the current timestamp when neither date bound was given and include_archived was off."
    • addedOutput schema / properties / appliedFilters / properties / preset
      Added value: +{
      +  "description": "ReliefWeb preset the query used: latest (current listings only, default) or analysis when include_archived.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / appliedFilters / required
      Previous value: -[
      -  "sort",
      -  "limit",
      -  "offset"
      -]New value: +[
      +  "sort",
      +  "preset",
      +  "limit",
      +  "offset"
      +]
  4. Changed8 schema fields changed
    • addedInput schema / properties / date_start_from / anyOf
      Added value: +[
      +  {
      +    "const": "",
      +    "type": "string"
      +  },
      +  {
      +    "description": "Calendar date (2024-06-01) or full ISO 8601 datetime (2024-06-01T00:00:00+00:00).",
      +    "pattern": "^\\d{4}-\\d{2}-\\d{2}(?:T\\d{2}:\\d{2}(?::\\d{2}(?:\\.\\d+)?)?(?:Z|[+-]\\d{2}:?\\d{2})?)?$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / date_start_from / description
      Previous value: -"Training start date lower bound (ISO 8601). Filters on date.start — use to find training starting after a given date."New value: +"Training 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."
    • removedInput schema / properties / date_start_from / type
      Removed value: -"string"
    • addedInput schema / properties / date_start_to / anyOf
      Added value: +[
      +  {
      +    "const": "",
      +    "type": "string"
      +  },
      +  {
      +    "description": "Calendar date (2024-12-31) or full ISO 8601 datetime (2024-12-31T23:59:59+00:00).",
      +    "pattern": "^\\d{4}-\\d{2}-\\d{2}(?:T\\d{2}:\\d{2}(?::\\d{2}(?:\\.\\d+)?)?(?:Z|[+-]\\d{2}:?\\d{2})?)?$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / date_start_to / description
      Previous value: -"Training start date upper bound (ISO 8601). Filters on date.start — pair with date_start_from for a window."New value: +"Training 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."
    • removedInput schema / properties / date_start_to / type
      Removed value: -"string"
    • changedOutput schema / properties / appliedFilters / properties / dateStartFrom / description
      Previous value: -"Training start date lower bound applied."New value: +"Training start date lower bound applied — the caller-supplied value, or the current timestamp when neither date bound was given."
    • changedOutput schema / properties / notice / description
      Previous value: -"Recovery hint when results are empty — echoes filters applied and suggests how to broaden."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."
  5. Changed1 schema field changed
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Sort 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.",
      +  "type": "string"
      +}
  6. Changed2 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"Training format (e.g., Workshop, E-learning, Conference, Seminar). Filters on format.name."New value: +"Training format. Valid values: on-site, online. Filters on format.name."
    • addedInput schema / properties / format / enum
      Added value: +[
      +  "on-site",
      +  "online"
      +]
  7. Changed2 schema fields changed
    • addedOutput schema / properties / appliedFilters
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "The resolved filter set the query actually ran with, after normalization and defaults. Echoes back so the agent can confirm how its inputs were interpreted.",
      +  "properties": {
      +    "careerCategory": {
      +      "description": "Career category name filter applied.",
      +      "type": "string"
      +    },
      +    "country": {
      +      "description": "Country code as normalized (uppercased ISO3).",
      +      "type": "string"
      +    },
      +    "dateStartFrom": {
      +      "description": "Training start date lower bound applied.",
      +      "type": "string"
      +    },
      +    "dateStartTo": {
      +      "description": "Training start date upper bound applied.",
      +      "type": "string"
      +    },
      +    "format": {
      +      "description": "Training format name filter applied.",
      +      "type": "string"
      +    },
      +    "language": {
      +      "description": "Language code filter applied.",
      +      "type": "string"
      +    },
      +    "limit": {
      +      "description": "Result limit the query used.",
      +      "type": "number"
      +    },
      +    "offset": {
      +      "description": "Pagination offset the query used.",
      +      "type": "number"
      +    },
      +    "sort": {
      +      "description": "Sort order the query used (resolved, including the default).",
      +      "type": "string"
      +    },
      +    "source": {
      +      "description": "Source short name filter applied.",
      +      "type": "string"
      +    },
      +    "text": {
      +      "description": "Full-text query the search used.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "sort",
      +    "limit",
      +    "offset"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "items",
      -  "totalCount"
      -]New value: +[
      +  "items",
      +  "appliedFilters",
      +  "totalCount"
      +]
  8. Changed3 schema fields changed
    • 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."
    • removedOutput schema / properties / message
      Removed value: -{
      -  "description": "Recovery hint when results are empty — echoes filters applied and suggests how to broaden.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Recovery hint when results are empty — echoes filters applied and suggests how to broaden.",
      +  "type": "string"
      +}
  9. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/open-world, and the description adds substantial non-obvious behavior: the injected 'start-from-now' default bound, default sort order, and the fact that include_archived drops that bound and reaches the whole record. It also flags that archived listings vastly outnumber current ones. This is exactly the kind of context annotations cannot convey.

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?

Dense and front-loaded with the facet list and date-field caveat first. There is mild redundancy in re-explaining the start-from-now default (both in the description body and in date_start_from), but every sentence carries useful information.

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 14-parameter, zero-required search tool with an output schema present, the description covers the critical edge cases an agent needs: default date scoping, sort default, and the archived-search caveat. Return values need not be explained since an output schema exists.

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 meaning beyond the schema by distinguishing training date fields (date.start/date.end) from report date fields and explaining the default sort behavior. The parameter-level detail is otherwise largely mirrored in the schema.

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 ('Search humanitarian training and learning opportunities on ReliefWeb') and enumerates the filterable facets. It is clearly distinguishable from siblings like reliefweb_search_reports and reliefweb_search_jobs, and the get_training sibling covers single-listing retrieval.

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?

Gives explicit when-to guidance: use date_start_from/date_start_to for a window, include_archived=true to include concluded listings, and explains that omitting both date bounds scopes to training starting from now. It lacks explicit naming of sibling alternatives (e.g., use get_training for a specific listing), which 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.