Skip to main content
Glama

Server Details

Search ReliefWeb humanitarian reports, disasters, jobs, training, and country profiles via MCP.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 64 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
cyanheads/reliefweb-mcp-server
GitHub Stars
1
Server Listing
@cyanheads/reliefweb-mcp-server

TDQS

A4.4/5.0

Scored across 11 tools

Disambiguation5/5

Each tool targets a clearly distinct resource type (country, disaster, job, report, training) combined with a distinct action (get, list, search). The get/search pairs are explicitly differentiated, with search returning summaries and get fetching full detail.

Naming Consistency5/5

Every tool follows the same reliefweb_verb_noun convention (get_country, search_reports, list_sources, etc.), with no mixing of casing or verb styles.

Tool Count5/5

Eleven tools is well-scoped for the domain, mapping cleanly onto five content types with search/get pairs plus two list helpers. Each tool earns its place with no redundancy.

Completeness4/5

Coverage is strong: search+get pairs exist for disasters, jobs, reports, and training, plus country browsing via get/list. Minor gaps remain, such as no direct get_source detail tool, but core workflows are fully served.

Available Tools

11 tools
reliefweb_get_countryGet ReliefWeb Country ProfileA
Read-onlyIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
iso3YesISO 3166-1 alpha-3 country code (e.g., SYR, AFG, UKR). Used to look up the country's ReliefWeb profile.
archiveNoArchive 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.
sectionsNoSections 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

ParametersJSON Schema
NameRequiredDescription
idNoReliefWeb numeric country ID.
iso3NoISO 3166-1 alpha-3 code.
kindNofull 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.
nameNoCountry name.
errorNoPresent when the call failed. Absent on success.
statusNoHumanitarian situation status.
archiveNoOne page of a curated list's archived entries, returned in place of the record.
sectionsNoEvery section of the record, largest first. Pass the names back in `sections` to retrieve them.
urlAliasNoCanonical ReliefWeb URL for this country page.
keyContentNoCurrently-active curated key content links maintained by ReliefWeb editors — the present curated set. The archived entries are reachable with archive: { list: "keyContent" }.
usefulLinksNoCurrently-active useful external links curated by ReliefWeb editors — the present set. The archived entries are reachable with archive: { list: "usefulLinks" }.
outlineNoticeNoHow to re-call this tool for specific sections of the record.
profileOverviewNoSituation overview text from the ReliefWeb editorial team.
appealsResponsePlansNoCurrently-active humanitarian appeals and response plans for this country — the present set. The archived entries are reachable with archive: { list: "appealsResponsePlans" }.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety/identity profile (readOnly, openWorld, idempotent), yet the description adds substantial behavior: budget-driven outline responses naming every section and its byte size, a firm 'Nothing is truncated on any path', archive pages never outlining because they carry no record prose, and the fact that profiles are OCHA-curated and omit archived entries.

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 the verb, resource, contents and the two selectors before deeper budget/archive detail; every sentence carries information (curation provenance, archive depth, outline behavior, no-truncation guarantee). Some sentences are long and packed, mildly reducing scannability.

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, so return payloads need no explanation, and the description covers the remaining gaps an agent needs: mutual exclusivity, the over-budget outline path, archive paging continuation, and non-truncation. Complete for a 3-parameter nested-schema tool.

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% and the schema already documents iso3, archive.list/limit/offset and pagination. The description still adds non-obvious semantics the schema does not foreground: the selectors are alternatives capped at one per call, archive skipped entries are exactly those the profile leaves out, and a 'sections' name not present on this record is rejected. Marginal but real added value above the baseline 3.

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 (a country profile from ReliefWeb) keyed by ISO3, and enumerates the profile's contents. It is immediately distinguishable from reliefweb_list_countries and from the other reliefweb_get_* siblings, which target disasters, jobs, reports and training.

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 routing rules between the two selectors: 'Two alternative selectors, at most one per call', with sections slicing the record and archive replacing it for archived entries the profile omits. It also states the omission case (omit sections for the whole record) and the rejection case (both together). It does not explicitly contrast itself with reliefweb_list_countries, which is the only remaining routing gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

reliefweb_get_disasterGet ReliefWeb DisasterA
Read-onlyIdempotent
Inspect

Fetch a disaster record by ReliefWeb numeric ID including description, affected countries, GLIDE number, profile overview, key content links, and active appeals or response plans. Use after reliefweb_search_disasters to retrieve full details. Each curated list also has an archive, which the record leaves out. Two alternative selectors, at most one per call: sections names parts of the record to return, archive pages one list's archived entries in place of the record. Description and profile overview can together run to tens of KB for major disasters. A record over the response budget comes back as a section outline naming every section and its byte size. Nothing is truncated on any path.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesReliefWeb numeric disaster ID. Obtained from reliefweb_search_disasters results.
archiveNoArchive mode: return a page of one curated list's ARCHIVED entries instead of the disaster 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.
sectionsNoSections of the disaster 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 record itself and never reaches archived entries — use archive for those.

Output Schema

ParametersJSON Schema
NameRequiredDescription
idNoReliefWeb numeric disaster ID.
kindNofull 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.
nameNoDisaster name.
errorNoPresent when the call failed. Absent on success.
glideNoGLIDE number for cross-system correlation.
typesNoDisaster type names.
statusNoDisaster status: alert, ongoing, past, or alert-archive.
archiveNoOne page of a curated list's archived entries, returned in place of the record.
sectionsNoEvery section of the record, largest first. Pass the names back in `sections` to retrieve them.
urlAliasNoCanonical ReliefWeb URL for this disaster.
countriesNoAll countries tagged on this disaster.
dateEventNoEvent date (ISO 8601), when available.
keyContentNoCurrently-active curated key content links from the ReliefWeb editorial team — the present curated set. The archived entries are reachable with archive: { list: "keyContent" }.
dateCreatedNoReliefWeb index date (ISO 8601).
descriptionNoFull disaster description text.
primaryTypeNoPrimary disaster type.
usefulLinksNoCurrently-active useful external links curated by ReliefWeb editors — the present set. The archived entries are reachable with archive: { list: "usefulLinks" }.
outlineNoticeNoHow to re-call this tool for specific sections of the record.
primaryCountryNoPrimary affected country.
profileOverviewNoProfile overview text from the ReliefWeb editorial team.
appealsResponsePlansNoCurrently-active appeals and response plans linked to this disaster — the present set. The archived entries are reachable with archive: { list: "appealsResponsePlans" }.

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing budget behavior (an over-budget record returns a section outline with per-section byte sizes), the guarantee that 'nothing is truncated on any path', that sparse records reject unknown section names, and that archive calls bypass the outline because they carry no record prose. These are the exact runtime surprises an agent would otherwise hit.

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 the core purpose followed by the search-then-fetch workflow, then the mode rules and the size caveat. It is dense and every sentence carries information, though several clauses (mutual exclusivity, archive paging mechanics) duplicate the nested schema descriptions.

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 a nested schema, an output schema, and safety annotations, the description covers the remaining unknowns: response-size handling, no-truncation guarantee, sparse-record rejection, and how the two selectors interact. An agent could call this correctly without opening anything else.

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, and the description adds genuine interaction semantics: sections and archive are alternatives, at most one per call, sections only names parts of the record and never reaches archived entries. It largely restates the schema's own nested descriptions, so it does not add a full level of new meaning.

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 disaster record by ReliefWeb numeric ID') and enumerates the payload (description, affected countries, GLIDE number, profile overview, key content links, appeals/response plans). It also distinguishes itself from siblings by naming reliefweb_search_disasters as the discovery step that precedes it.

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_disasters to retrieve full details', and lays out the selection rules for its two modes: sections returns parts of the record, archive pages one list's archived entries instead. It states they are mutually exclusive and that supplying both is rejected, so an agent knows exactly which mode to pick.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

reliefweb_get_jobGet ReliefWeb JobA
Read-onlyIdempotent
Inspect

Fetch a job posting by ReliefWeb numeric ID with the full vacancy description, application instructions, dates, hiring organization, and location and taxonomy metadata. Use after reliefweb_search_jobs, which returns summaries without the description or application instructions. Reaches expired postings as well as open ones. 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesReliefWeb numeric job ID. Obtained from reliefweb_search_jobs results.
sectionsNoSections of the job 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

ParametersJSON Schema
NameRequiredDescription
idNoReliefWeb numeric job ID.
urlNoReliefWeb node URL for this job listing.
bodyNoFull vacancy description (HTML) — duties, requirements, and conditions.
kindNofull 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.
errorNoPresent when the call failed. Absent on success.
titleNoJob title.
typesNoJob type names, such as Job or Consultancy.
statusNoPosting status: published while the vacancy is open, expired once it has closed.
themesNoHumanitarian theme/sector names.
sourcesNoHiring organizations (short names).
sectionsNoEvery section of the record, largest first. Pass the names back in `sections` to retrieve them.
urlAliasNoCanonical ReliefWeb URL for this job listing.
countriesNoCountries tagged on this job.
howToApplyNoApplication instructions (HTML) as published by the hiring organization.
dateChangedNoDate this posting was last modified (ISO 8601).
dateClosingNoApplication closing date (ISO 8601).
dateCreatedNoDate this posting was indexed (ISO 8601).
outlineNoticeNoHow to re-call this tool for specific sections of the record.
careerCategoriesNoCareer category names (humanitarian tracks).
experienceLevelsNoRequired experience levels.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, but the description adds behavior the annotations do not: expired postings are still reachable, oversized records return a section outline with per-section byte sizes instead of data, and nothing is truncated on either path. That is exactly the extra operational context an agent needs.

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?

Four sentences, front-loaded with the fetch and its payload, then the routing advice, then the edge-case behavior. Every sentence carries information an agent needs; nothing is 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, so return values need no prose. Between the description's outline/budget behavior and the schema's parameter documentation, an agent has everything required to call and interpret this tool correctly.

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%, and the schema's own text for sections (rejection of unknown names, identity metadata always returned, self-contained re-fetch) is at least as detailed as the description. The description adds only the re-call workflow, so baseline 3 is appropriate.

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 (a job posting by ReliefWeb numeric ID) and enumerates what the record contains: vacancy description, application instructions, dates, hiring organization, location and taxonomy metadata. This lets an agent distinguish it from reliefweb_get_report, reliefweb_get_training and the search siblings without opening any 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 names the sibling to call first and the condition that selects this tool: "Use after reliefweb_search_jobs, which returns summaries without the description or application instructions." It also notes it reaches expired postings, widening the applicable context. It does not state a when-not case, so it stops short of the full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

reliefweb_get_reportGet ReliefWeb ReportA
Read-onlyIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesReliefWeb numeric report ID. Obtained from reliefweb_search_reports results.
sectionsNoSections 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

ParametersJSON Schema
NameRequiredDescription
idNoReliefWeb numeric report ID.
bodyNoFull report body text (HTML). Present for most reports; absent for binary-only documents.
kindNofull 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.
errorNoPresent when the call failed. Absent on success.
titleNoReport title.
themesNoHumanitarian theme/sector names.
formatsNoContent format names.
sourcesNoPublishing organizations (short names).
fileUrlsNoDirect file download URLs attached to this report.
sectionsNoEvery section of the record, largest first. Pass the names back in `sections` to retrieve them.
urlAliasNoCanonical ReliefWeb URL for this report.
countriesNoAll countries tagged on this report.
languagesNoLanguage codes (ISO 639-1).
dateCreatedNoReliefWeb index date (ISO 8601).
dateOriginalNoSource publication date (ISO 8601).
outlineNoticeNoHow to re-call this tool for specific sections of the record.
primaryCountryNoPrimary country name for this report.
headlineSummaryNoShort editorial summary from the headline block, when present.

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.

reliefweb_get_trainingGet ReliefWeb TrainingA
Read-onlyIdempotent
Inspect

Fetch a training listing by ReliefWeb numeric ID with the full description, registration instructions, event link, cost and fee information, dates, languages, and organizing source. Use after reliefweb_search_training, which returns summaries without the description, registration instructions, or cost detail. Reaches concluded listings as well as current ones. 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesReliefWeb numeric training ID. Obtained from reliefweb_search_training results.
sectionsNoSections of the training 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

ParametersJSON Schema
NameRequiredDescription
idNoReliefWeb numeric training ID.
urlNoReliefWeb node URL for this training listing.
bodyNoFull training description (HTML) — content, audience, and logistics.
costNoCost class as ReliefWeb records it, such as free or fee-based.
kindNofull 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.
errorNoPresent when the call failed. Absent on success.
titleNoTraining title.
typesNoTraining type names, such as Training/Workshop or Course.
citiesNoHost cities, for on-site training.
statusNoListing status: published while the training is current, expired once concluded.
themesNoHumanitarian theme/sector names.
dateEndNoTraining end date (ISO 8601).
formatsNoTraining format names: on-site or online.
sourcesNoOrganizing organizations (short names).
eventUrlNoThe organizer's own page for this training, when published.
sectionsNoEvery section of the record, largest first. Pass the names back in `sections` to retrieve them.
urlAliasNoCanonical ReliefWeb URL for this training listing.
countriesNoCountries tagged on this training.
dateStartNoTraining start date (ISO 8601).
languagesNoLanguage codes of the listing (ISO 639-1).
dateCreatedNoDate this listing was indexed (ISO 8601).
howToRegisterNoRegistration instructions (HTML) as published by the organizer.
outlineNoticeNoHow to re-call this tool for specific sections of the record.
feeInformationNoFee detail as published by the organizer — amounts, inclusions, and conditions.
careerCategoriesNoCareer category names (humanitarian tracks).
dateRegistrationNoRegistration deadline (ISO 8601).
trainingLanguagesNoLanguage codes the training is delivered in (ISO 639-1).

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld), and the description adds genuinely new behavior: over-budget records return a section outline with byte sizes, and nothing is ever truncated on either path. That is operationally important context an agent cannot get from the annotations.

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 and sibling routing, then the fallback behavior; every sentence carries information. It is slightly dense with detail but nothing is redundant or wasted.

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, so return values need no re-explanation, yet the description still covers the two-path response behavior and the self-contained re-fetch guarantee. Nothing an agent needs to call this 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: the outline-and-re-call workflow for sections, rejection of section names the sparse record lacks, and the guarantee that identity metadata always accompanies the request.

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 (training listing by numeric ID), then enumerates the fields it carries. It clearly distinguishes itself from reliefweb_search_training, which is named and characterized as returning only summaries.

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_training and explains why (search lacks description, registration instructions, cost detail). It also notes coverage of concluded listings, giving the agent a clear trigger condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

reliefweb_list_countriesList ReliefWeb CountriesA
Read-onlyIdempotent
Inspect

List all countries and territories tracked by ReliefWeb, optionally filtered to active humanitarian situations. Returns ISO3 codes and status for each entry — use the ISO3 code with reliefweb_get_country to fetch a full profile. Set crisis_only=true to limit results to countries with active humanitarian situations.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (1–1000, default 100). Each call counts against the 1,000-calls/day quota.
offsetNoZero-based offset for pagination. Use with limit and the totalCount enrichment field to page through results.
crisis_onlyNoWhen true, filters to countries with an active humanitarian situation (status ongoing). Default false returns all countries.

Output Schema

ParametersJSON Schema
NameRequiredDescription
errorNoPresent when the call failed. Absent on success.
itemsNoCountries tracked by ReliefWeb.
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 countries matching the filter before pagination.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly, openWorld, and idempotent hints. The description adds valuable behavioral context by stating what is returned (ISO3 codes and status) and how the optional filter affects results ('crisis_only=true to limit results to countries with active humanitarian situations'). This goes beyond the annotations without contradicting them.

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?

Two sentences with no filler. The core function and output are front-loaded, followed by the filter usage and a pointer to the sibling. Every word contributes value.

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 the output schema exists and annotations cover safety, the description is sufficient. It mentions the key output fields, the optional filter, and points to the sibling for full details. The pagination and rate limit are already in the schema, so nothing critical is missing.

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 coverage is 100% with detailed descriptions for limit, offset, and crisis_only, so the description adds little beyond reminding the agent to use crisis_only. The baseline is 3 because the schema carries the parameter semantics; the description does not introduce new meaning beyond 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?

The description states a specific verb ('List') and resource ('all countries and territories tracked by ReliefWeb'), distinguishes from the sibling reliefweb_get_country by noting it returns a list, and clarifies the optional crisis filter. This clearly differentiates it from the other list/search tools.

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 provides an explicit alternative: 'use the ISO3 code with reliefweb_get_country to fetch a full profile.' It also gives a usage condition for crisis_only. However, it does not explicitly state when NOT to use this tool compared to the search tools (e.g., when a country-specific query is needed), but the given guidance is sufficient for the main alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

reliefweb_list_sourcesList ReliefWeb SourcesA
Read-onlyIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
textNoFull-text search query. Matches against organization name and short name.
typeNoOrganization type. One of: Non-governmental Organization, International Organization, Academic and Research Institution, Other, Government, Media, Red Cross/Red Crescent Movement. Filters on type.name.
limitNoNumber of results to return (1–1000, default 10). Each call counts against the 1,000-calls/day quota.
offsetNoZero-based offset for pagination. Use with limit and the totalCount enrichment field to page through results.

Output Schema

ParametersJSON Schema
NameRequiredDescription
errorNoPresent when the call failed. Absent on success.
itemsNoSource organizations contributing content to ReliefWeb.
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 sources matching the query before pagination.

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.

reliefweb_search_disastersSearch ReliefWeb DisastersA
Read-onlyIdempotent
Inspect

Search active and historical disasters on ReliefWeb by type, country, status, date range, and GLIDE number. Default preset covers alert, ongoing, and past disasters. Use include_archived=true to reach alert-archive entries as well, for historical research. Returns IDs suitable for use with reliefweb_get_disaster and as disaster_id filter in reliefweb_search_reports.

ParametersJSON Schema
NameRequiredDescriptionDefault
sortNoSort order. Use date.created:desc for newest first (default), date.created:asc for oldest, score:desc for relevance.
textNoFull-text search query. Matches against disaster name and description.
glideNoGLIDE number (global disaster identifier, e.g., EQ-2023-000053-TUR). Use for cross-system disaster correlation.
limitNoNumber of results to return (1–1000, default 10). Each call counts against the 1,000-calls/day quota.
offsetNoZero-based offset for pagination. Use with limit and the totalCount enrichment field to page through results.
statusNoDisaster status filter. One of: alert (newly declared), ongoing, past (resolved), alert-archive. Separate multiple values with commas; case, spacing, and punctuation are ignored, and any other value is rejected with the valid list. alert-archive is only reachable with include_archived=true — asking for it without that returns nothing.
countryNoISO 3166-1 alpha-3 country code (e.g., SYR, AFG, UKR). Filters to disasters tagged with this country.
date_toNoLatest disaster creation date. Pair with date_from for a date range. A bare calendar date resolves to end of that day in UTC, so the range covers it in full; a datetime carrying any offset is resolved to UTC.
date_fromNoEarliest disaster creation date. Filters on date.created. A bare calendar date such as 2024-01-15 is accepted and resolves to start of that day in UTC; a datetime carrying any offset is resolved to UTC.
disaster_typeNoDisaster type name (e.g., Earthquake, Flood, Drought, Cyclone). Filters on type.name.
include_archivedNoInclude alert-archive disasters in results, alongside alert, ongoing, and past. Uses preset=analysis. Off by default.

Output Schema

ParametersJSON Schema
NameRequiredDescription
errorNoPresent when the call failed. Absent on success.
itemsNoMatching disasters.
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 disasters 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.5/5.0
Behavior5/5

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

Adds significant detail beyond annotations: default preset behavior, archived reachability, quota limit per call (1,000/day), status value validation, and date resolution semantics. The readOnlyHint and idempotentHint are already present, and the description complements them with operational behavior like pagination via totalCount enrichment field.

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?

Two sentences, front-loaded with purpose, followed by a critical filtering nuance and a chaining hint. Every sentence earns its place with no redundancy or 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?

Given the 11-parameter complexity, an output schema for results, and read-only/idempotent annotations, the description covers all essential aspects: defaults, archived behavior, quota, date handling, and downstream usage. An agent has sufficient information to invoke correctly without additional lookups.

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% and each parameter's meaning is already documented thoroughly in the schema. The tool description repeats the overall filter categories but does not add new semantic detail beyond what the schema provides. Baseline of 3 is appropriate.

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 specific verb ('search'), resource ('disasters on ReliefWeb'), and the filter criteria (type, country, status, date range, GLIDE number). It differentiates from sibling tools by mentioning returned IDs suitable for reliefweb_get_disaster and as disaster_id filter in reliefweb_search_reports, establishing its role in a workflow.

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 clear guidance on when to use include_archived=true for historical research and default preset coverage. Names related siblings for chaining. However, it does not explicitly state when to prefer this search over reliefweb_get_disaster for single-record retrieval, leaving some inference to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

reliefweb_search_jobsSearch ReliefWeb JobsA
Read-onlyIdempotent
Inspect

Search humanitarian job listings on ReliefWeb by country, organization, career category, theme, and experience level. Returns current open positions — expired postings are excluded by default. Use include_archived=true to search the full history of postings, which is far larger than the open set. Use text search for role titles and job descriptions.

ParametersJSON Schema
NameRequiredDescriptionDefault
sortNoSort order. Use date.created:desc for newest postings first (default), date.closing:asc to surface roles closing soonest, or score:desc for relevance.
textNoFull-text search query. Matches against job title, body, and key metadata fields.
limitNoNumber of results to return (1–1000, default 10). Each call counts against the 1,000-calls/day quota.
themeNoSector or cross-cutting theme (e.g., Health, Food and Nutrition, Protection). Filters on theme.name.
offsetNoZero-based offset for pagination. Use with limit and the totalCount enrichment field to page through results.
sourceNoOrganization short name (e.g., UNHCR, OCHA, WFP). Filters on source.shortname.
countryNoISO 3166-1 alpha-3 country code (e.g., SYR, AFG, UKR). Filters to jobs tagged with this country.
experienceNoExperience level (e.g., 0-2 years, 3-4 years, 5-9 years). Filters on experience.name.
career_categoryNoHumanitarian career track (e.g., Programme and Project Management, Information and Communications Technology, Logistics and Telecommunications). Filters on career_categories.name.
include_archivedNoSearch expired postings alongside the open ones. Uses preset=analysis. Off by default — the open set is a small fraction of the archive, so turn this on for labour-market history rather than for a hiring snapshot.

Output Schema

ParametersJSON Schema
NameRequiredDescription
errorNoPresent when the call failed. Absent on success.
itemsNoMatching job listings.
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 jobs 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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful behavioral context: expired postings are excluded by default, the archived set is 'far larger', and include_archived uses preset=analysis. These details go beyond annotations and clarify the default scope and the trade-off of turning on archiving.

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 four succinct sentences, all informative. It front-loads the main purpose and filters, then covers the default behavior, the archived option, and the text search hint. Every sentence earns its place 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?

For a search tool with ten well-documented parameters, an output schema, and annotations that cover safety, the description is complete. It resolves the key ambiguity between open and archived postings, provides scaling context, and gives practical usage guidance. Nothing an agent needs to call 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 parameters are fully documented. The description adds semantic value for include_archived by explaining its purpose (searching full history) and the scale difference, and for text by stating it matches titles and descriptions. These enrich the schema descriptions without redundancy.

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 the verb 'Search' and the resource 'humanitarian job listings on ReliefWeb', identifies the filtering dimensions (country, organization, career category, theme, experience level), and explicitly notes that it returns current open positions with expired postings excluded by default. It distinguishes itself from sibling tools like get_job by implying a search over a set rather than a single record.

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 clear context for when to enable include_archived (for full history vs. current snapshot) and when to use text search (for role titles and job descriptions). However, it does not explicitly mention alternatives like get_job for fetching a single job by ID, so the routing to siblings is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

reliefweb_search_reportsSearch ReliefWeb ReportsA
Read-onlyIdempotent
Inspect

Search humanitarian reports on ReliefWeb with filtering by country, disaster, format, theme, language, source, and date. Returns paginated summaries — use reliefweb_get_report to fetch full body text. Report body is excluded from results (10–100KB each); call get_report when document content is needed. Every report is reachable by default — reports have no archived class, so include_archived has no effect here. Note: each call counts against the 1,000 calls/day quota.

ParametersJSON Schema
NameRequiredDescriptionDefault
sortNoSort order. Use date.original:desc for newest first (default), date.original:asc for oldest first, score:desc for relevance.
textNoFull-text search query. Matches against title, body, and key metadata fields. Use plain natural language or keywords.
limitNoNumber of results to return (1–1000, default 10). Use a smaller value for targeted lookups; larger for bulk research. Each call counts against the 1,000-calls/day quota.
themeNoSector or cross-cutting theme (e.g., Health, Food and Nutrition, Shelter and Non-Food Items, Protection). Open-ended — matches theme.name exactly as ReliefWeb spells it.
filterNoRaw ReliefWeb filter object for compound conditions not covered by named params. Example: {"operator": "AND", "conditions": [{"field": "format.name", "value": "Map"}, {"field": "language.code", "value": "fr"}]}.
formatNoContent format filter. One of: News and Press Release, Situation Report, Map, Infographic, Analysis, Other, Assessment, Manual and Guideline, Appeal, UN Document, Evaluation and Lessons Learned. Case, spacing, and punctuation are ignored; any other value is rejected with the valid list.
offsetNoZero-based offset for pagination. Use with limit and the totalCount enrichment field to page through large result sets.
sourceNoOrganization short name (e.g., UNHCR, OCHA, WFP). Filters on source.shortname.
countryNoISO 3166-1 alpha-3 country code (e.g., SYR, AFG, UKR). Filters to content tagged with this country.
date_toNoLatest publication date. Pair with date_from for a date range. A bare calendar date resolves to end of that day in UTC, so the range covers it in full; a datetime carrying any offset is resolved to UTC.
languageNoISO 639-1 language code (e.g., en, fr, es, ar). Filters on language.code.
date_fromNoEarliest publication date. Filters on date.original (source publication date). A bare calendar date such as 2024-01-15 is accepted and resolves to start of that day in UTC; a datetime carrying any offset is resolved to UTC.
disaster_idNoReliefWeb numeric disaster ID. Filters to reports linked to a specific disaster. Get the ID from reliefweb_search_disasters.
include_archivedNoNo effect on reports. Reports have no archived class — every report is already in scope, whatever this is set to. Kept so existing calls that pass it keep working; it is meaningful on reliefweb_search_jobs, reliefweb_search_training, and reliefweb_search_disasters.

Output Schema

ParametersJSON Schema
NameRequiredDescription
errorNoPresent when the call failed. Absent on success.
itemsNoMatching reports (summaries only — use reliefweb_get_report for full body).
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 reports 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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it notes that report bodies are excluded from results (with size estimates), that include_archived has no effect on reports, and that each call counts against a 1,000/day quota. This gives the agent important operational constraints not evident from annotations.

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?

The description is concise given the tool's complexity (14 parameters, many with nuanced behavior). It front-loads the core purpose and quickly notes the key limitation (no body text, use get_report). Every sentence serves a purpose—mentioning pagination, quota, and include_archived behavior. It's structured logically but could be slightly tightened to avoid repeating 'each call counts' twice, though that repetition reinforces an important constraint.

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?

This is a complex tool with 14 parameters, nested objects, and an output schema. The description covers the essential operational details: what the tool returns (paginated summaries without body text), when to use the sibling get_report, the archiving caveat, the quota impact, and how to page. The output schema likely describes the response structure, so the description doesn't need to enumerate return fields. It's complete for an agent to correctly invoke it.

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 coverage is 100% and every parameter has a description. The description adds modest extra value beyond the schema—for instance, it explains that the text parameter matches against title, body, and metadata, and it clarifies the behavior of date_from/date_to with timezone resolution. However, most parameter details are already in the schema, so the baseline of 3 is appropriate; the description doesn't significantly elevate parameter understanding beyond what's 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?

The description clearly states the tool searches humanitarian reports with specific filters (country, disaster, format, theme, language, source, date) and returns paginated summaries. It distinguishes itself from sibling tools by explicitly mentioning reliefweb_get_report for full body text, which separates search from 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?

It provides solid guidance on when to use this tool versus reliefweb_get_report (when full body is needed) and explains that include_archived has no effect on reports, directing users to sibling tools where it is meaningful. However, it doesn't explicitly state when to prefer this over reliefweb_search_disasters or other search tools, though the 'search reports' focus implicitly covers it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

reliefweb_search_trainingSearch ReliefWeb TrainingA
Read-onlyIdempotent
Inspect

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.

ParametersJSON 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

ParametersJSON Schema
NameRequiredDescription
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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 5 tool updates
    • Changedreliefweb_get_country1 field changed
      • 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."
    • Changedreliefweb_get_disaster1 field changed
      • changedInput schema / properties / sections / description
        Previous value: -"Sections of the disaster 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 record itself and never reaches archived entries — use archive for those."New value: +"Sections of the disaster 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 record itself and never reaches archived entries — use archive for those."
    • Changedreliefweb_get_job1 field changed
      • changedInput schema / properties / sections / description
        Previous value: -"Sections of the job 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 job 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."
    • Changedreliefweb_get_report1 field changed
      • 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."
    • Changedreliefweb_get_training1 field changed
      • changedInput schema / properties / sections / description
        Previous value: -"Sections of the training 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 training 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."
  2. 11 tool updates
    • Changedreliefweb_get_country6 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": [
        +      "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"
        -]
    • Changedreliefweb_get_disaster6 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": [
        +      "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 disaster found with the given ID. `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"
        -]
    • Changedreliefweb_get_job6 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": [
        +      "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 job posting 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"
        -]
    • Changedreliefweb_get_report6 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": [
        +      "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"
        -]
    • Changedreliefweb_get_training6 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": [
        +      "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 training listing 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"
        -]
    • Changedreliefweb_list_countries6 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",
        +      "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"
        -]
    • Changedreliefweb_list_sources6 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",
        +      "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"
        -]
    • Changedreliefweb_search_disasters6 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: `unknown_status`: A status token does not name a ReliefWeb disaster status. `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": [
        +            "unknown_status",
        +            "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"
        -]
    • Changedreliefweb_search_jobs6 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 — typically an unrecognized sort field. `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"
        -]
    • Changedreliefweb_search_reports6 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: `unknown_format`: The format value does not name a ReliefWeb report format. `invalid_query`: ReliefWeb rejected the query — an unrecognized sort field, an invalid raw filter object, 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": [
        +            "unknown_format",
        +            "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"
        -]
    • Changedreliefweb_search_training6 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. 5 tool updates
    • Changedreliefweb_get_country10 fields changed
      • 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"
        +]
    • Changedreliefweb_get_disaster10 fields changed
      • addedInput schema / properties / archive
        Added value: +{
        +  "description": "Archive mode: return a page of one curated list's ARCHIVED entries instead of the disaster 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 disaster 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 record 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 appeals and response plans linked to this disaster — the present set, not the full historical archive."New value: +"Currently-active appeals and response plans linked to this disaster — 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 from the ReliefWeb editorial team — the present curated set, not the full historical archive."New value: +"Currently-active curated key content links from the ReliefWeb editorial team — 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"
        +]
    • Addedreliefweb_get_job
    • Changedreliefweb_get_report5 fields changed
      • 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"
        +]
    • Addedreliefweb_get_training
  4. 5 tool updates
    • Changedreliefweb_get_disaster1 field changed
      • changedOutput schema / properties / status / description
        Previous value: -"Disaster status (alert, current, past, archive)."New value: +"Disaster status: alert, ongoing, past, or alert-archive."
    • Changedreliefweb_search_disasters4 fields changed
      • changedInput schema / properties / include_archived / description
        Previous value: -"Include alert-archive and archive disasters in results. Uses preset=analysis. Off by default."New value: +"Include alert-archive disasters in results, alongside alert, ongoing, and past. Uses preset=analysis. Off by default."
      • changedInput schema / properties / status / description
        Previous value: -"Disaster status filter. Values: alert (newly declared), current (ongoing), past (resolved), alert-archive, archive. Separate multiple values with commas. Default preset includes alert, current, past."New value: +"Disaster status filter. One of: alert (newly declared), ongoing, past (resolved), alert-archive. Separate multiple values with commas; case, spacing, and punctuation are ignored, and any other value is rejected with the valid list. alert-archive is only reachable with include_archived=true — asking for it without that returns nothing."
      • changedOutput schema / properties / appliedFilters / properties / status / description
        Previous value: -"Status filter applied (comma-joined when multiple)."New value: +"Status filter applied, in canonical spelling (comma-joined when multiple)."
      • changedOutput schema / properties / items / items / properties / status / description
        Previous value: -"Disaster status (alert, current, past, archive)."New value: +"Disaster status: alert, ongoing, past, or alert-archive."
    • Changedreliefweb_search_jobs3 fields changed
      • addedInput schema / properties / include_archived
        Added value: +{
        +  "description": "Search expired postings alongside the open ones. Uses preset=analysis. Off by default — the open set is a small fraction of the archive, so turn this on for labour-market history rather than for a hiring snapshot.",
        +  "type": "boolean"
        +}
      • addedOutput schema / properties / appliedFilters / properties / preset
        Added value: +{
        +  "description": "ReliefWeb preset the query used: latest (open postings 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"
        +]
    • Changedreliefweb_search_reports5 fields changed
      • changedInput schema / properties / format / description
        Previous value: -"Content format filter. Valid values: Situation Report, Assessment, Analysis, Map, Infographic, Manual and Guideline, News and Press Release, Policy Document, Appeal, Financial Report, Evaluation and Lessons Learned, Other."New value: +"Content format filter. One of: News and Press Release, Situation Report, Map, Infographic, Analysis, Other, Assessment, Manual and Guideline, Appeal, UN Document, Evaluation and Lessons Learned. Case, spacing, and punctuation are ignored; any other value is rejected with the valid list."
      • changedInput schema / properties / include_archived / description
        Previous value: -"Include archived and to-review content in addition to published. Uses preset=analysis. Off by default."New value: +"No effect on reports. Reports have no archived class — every report is already in scope, whatever this is set to. Kept so existing calls that pass it keep working; it is meaningful on reliefweb_search_jobs, reliefweb_search_training, and reliefweb_search_disasters."
      • changedInput schema / properties / theme / description
        Previous value: -"Sector or cross-cutting theme (e.g., Health, Food and Nutrition, Shelter and NFI, Protection). Matches theme.name."New value: +"Sector or cross-cutting theme (e.g., Health, Food and Nutrition, Shelter and Non-Food Items, Protection). Open-ended — matches theme.name exactly as ReliefWeb spells it."
      • changedOutput schema / properties / appliedFilters / properties / format / description
        Previous value: -"Format name filter applied."New value: +"Format name filter applied, in its canonical ReliefWeb spelling."
      • changedOutput schema / properties / appliedFilters / properties / preset / description
        Previous value: -"ReliefWeb preset the query used: latest (default) or analysis when include_archived."New value: +"ReliefWeb preset the query used. Always latest for reports — no preset changes which reports match."
    • Changedreliefweb_search_training5 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"
        +]
  5. 6 tool updates
    • Changedreliefweb_list_countries1 field changed
      • changedOutput schema / properties / notice / description
        Previous value: -"Recovery hint when results are empty — echoes the active filter 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."
    • Changedreliefweb_list_sources1 field changed
      • 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."
    • Changedreliefweb_search_disasters7 fields changed
      • addedInput schema / properties / date_from / anyOf
        Added value: +[
        +  {
        +    "const": "",
        +    "type": "string"
        +  },
        +  {
        +    "description": "Calendar date (2024-01-15) or full ISO 8601 datetime (2024-01-15T00: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_from / description
        Previous value: -"Earliest disaster creation date (ISO 8601). Filters on date.created."New value: +"Earliest disaster creation date. Filters on date.created. A bare calendar date such as 2024-01-15 is accepted and resolves to start of that day in UTC; a datetime carrying any offset is resolved to UTC."
      • removedInput schema / properties / date_from / type
        Removed value: -"string"
      • addedInput schema / properties / date_to / anyOf
        Added value: +[
        +  {
        +    "const": "",
        +    "type": "string"
        +  },
        +  {
        +    "description": "Calendar date (2024-01-31) or full ISO 8601 datetime (2024-01-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_to / description
        Previous value: -"Latest disaster creation date (ISO 8601). Pair with date_from for a date range."New value: +"Latest disaster creation date. Pair with date_from for a date range. A bare calendar date resolves to end of that day in UTC, so the range covers it in full; a datetime carrying any offset is resolved to UTC."
      • removedInput schema / properties / date_to / type
        Removed value: -"string"
      • 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."
    • Changedreliefweb_search_jobs1 field changed
      • 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."
    • Changedreliefweb_search_reports7 fields changed
      • addedInput schema / properties / date_from / anyOf
        Added value: +[
        +  {
        +    "const": "",
        +    "type": "string"
        +  },
        +  {
        +    "description": "Calendar date (2024-01-15) or full ISO 8601 datetime (2024-01-15T00: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_from / description
        Previous value: -"Earliest publication date (ISO 8601, e.g., 2024-01-15T00:00:00+00:00). Filters on date.original (source publication date)."New value: +"Earliest publication date. Filters on date.original (source publication date). A bare calendar date such as 2024-01-15 is accepted and resolves to start of that day in UTC; a datetime carrying any offset is resolved to UTC."
      • removedInput schema / properties / date_from / type
        Removed value: -"string"
      • addedInput schema / properties / date_to / anyOf
        Added value: +[
        +  {
        +    "const": "",
        +    "type": "string"
        +  },
        +  {
        +    "description": "Calendar date (2024-01-31) or full ISO 8601 datetime (2024-01-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_to / description
        Previous value: -"Latest publication date (ISO 8601). Pair with date_from for a date range."New value: +"Latest publication date. Pair with date_from for a date range. A bare calendar date resolves to end of that day in UTC, so the range covers it in full; a datetime carrying any offset is resolved to UTC."
      • removedInput schema / properties / date_to / type
        Removed value: -"string"
      • changedOutput schema / properties / notice / description
        Previous value: -"Recovery hint when results are empty — echoes the filters applied 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."
    • Changedreliefweb_search_training8 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."
  6. 4 tool updates
    • Changedreliefweb_get_country3 fields changed
      • 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."
    • Changedreliefweb_get_disaster3 fields changed
      • changedOutput schema / properties / appealsResponsePlans / description
        Previous value: -"Active appeals and response plans linked to this disaster."New value: +"Currently-active appeals and response plans linked to this disaster — the present set, not the full historical archive."
      • changedOutput schema / properties / keyContent / description
        Previous value: -"Curated key content links from the ReliefWeb editorial team."New value: +"Currently-active curated key content links from the ReliefWeb editorial team — 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."
    • Changedreliefweb_search_jobs1 field changed
      • addedInput schema / properties / sort
        Added value: +{
        +  "description": "Sort order. Use date.created:desc for newest postings first (default), date.closing:asc to surface roles closing soonest, or score:desc for relevance.",
        +  "type": "string"
        +}
    • Changedreliefweb_search_training1 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"
        +}
  7. 4 tool updates
    • Changedreliefweb_list_countries2 fields changed
      • changedInput schema / properties / crisis_only / description
        Previous value: -"When true, filters to countries with an active humanitarian situation (status alert or current). Default false returns all countries."New value: +"When true, filters to countries with an active humanitarian situation (status ongoing). Default false returns all countries."
      • changedOutput schema / properties / items / items / properties / status / description
        Previous value: -"Humanitarian situation status. Active situations have status alert or current."New value: +"Humanitarian situation status: ongoing (active crisis) or normal (non-crisis)."
    • Changedreliefweb_list_sources2 fields changed
      • 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"
        +]
    • Changedreliefweb_search_disasters1 field changed
      • changedInput schema / properties / country / description
        Previous value: -"ISO 3166-1 alpha-3 country code (e.g., SYR, AFG, UKR). Filters to disasters tagged with this primary country."New value: +"ISO 3166-1 alpha-3 country code (e.g., SYR, AFG, UKR). Filters to disasters tagged with this country."
    • Changedreliefweb_search_training2 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"
        +]
  8. 6 tool updates
    • Changedreliefweb_list_countries1 field changed
      • addedOutput schema / properties / notice
        Added value: +{
        +  "description": "Recovery hint when results are empty — echoes the active filter and suggests how to broaden. Absent on successful result pages.",
        +  "type": "string"
        +}
    • Changedreliefweb_list_sources1 field changed
      • 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"
        +}
    • Changedreliefweb_search_disasters2 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": {
        +    "country": {
        +      "description": "Country code as normalized (uppercased ISO3).",
        +      "type": "string"
        +    },
        +    "dateFrom": {
        +      "description": "Earliest creation date filter applied.",
        +      "type": "string"
        +    },
        +    "dateTo": {
        +      "description": "Latest creation date filter applied.",
        +      "type": "string"
        +    },
        +    "disasterType": {
        +      "description": "Disaster type name filter applied.",
        +      "type": "string"
        +    },
        +    "glide": {
        +      "description": "GLIDE number filter applied.",
        +      "type": "string"
        +    },
        +    "limit": {
        +      "description": "Result limit the query used.",
        +      "type": "number"
        +    },
        +    "offset": {
        +      "description": "Pagination offset the query used.",
        +      "type": "number"
        +    },
        +    "preset": {
        +      "description": "ReliefWeb preset the query used: latest (default) or analysis when include_archived.",
        +      "type": "string"
        +    },
        +    "sort": {
        +      "description": "Sort order the query used (resolved, including the default).",
        +      "type": "string"
        +    },
        +    "status": {
        +      "description": "Status filter applied (comma-joined when multiple).",
        +      "type": "string"
        +    },
        +    "text": {
        +      "description": "Full-text query the search used.",
        +      "type": "string"
        +    }
        +  },
        +  "required": [
        +    "sort",
        +    "preset",
        +    "limit",
        +    "offset"
        +  ],
        +  "type": "object"
        +}
      • changedOutput schema / required
        Previous value: -[
        -  "items",
        -  "totalCount"
        -]New value: +[
        +  "items",
        +  "appliedFilters",
        +  "totalCount"
        +]
    • Changedreliefweb_search_jobs2 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"
        +    },
        +    "experience": {
        +      "description": "Experience level 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"
        +    },
        +    "theme": {
        +      "description": "Theme name filter applied.",
        +      "type": "string"
        +    }
        +  },
        +  "required": [
        +    "sort",
        +    "limit",
        +    "offset"
        +  ],
        +  "type": "object"
        +}
      • changedOutput schema / required
        Previous value: -[
        -  "items",
        -  "totalCount"
        -]New value: +[
        +  "items",
        +  "appliedFilters",
        +  "totalCount"
        +]
    • Changedreliefweb_search_reports2 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": {
        +    "country": {
        +      "description": "Country code as normalized (uppercased ISO3).",
        +      "type": "string"
        +    },
        +    "dateFrom": {
        +      "description": "Earliest publication date filter applied.",
        +      "type": "string"
        +    },
        +    "dateTo": {
        +      "description": "Latest publication date filter applied.",
        +      "type": "string"
        +    },
        +    "disasterId": {
        +      "description": "Disaster ID filter applied.",
        +      "type": "number"
        +    },
        +    "format": {
        +      "description": "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"
        +    },
        +    "preset": {
        +      "description": "ReliefWeb preset the query used: latest (default) or analysis when include_archived.",
        +      "type": "string"
        +    },
        +    "rawFilter": {
        +      "description": "True when a raw compound filter object was merged into the query.",
        +      "type": "boolean"
        +    },
        +    "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"
        +    },
        +    "theme": {
        +      "description": "Theme name filter applied.",
        +      "type": "string"
        +    }
        +  },
        +  "required": [
        +    "sort",
        +    "preset",
        +    "limit",
        +    "offset"
        +  ],
        +  "type": "object"
        +}
      • changedOutput schema / required
        Previous value: -[
        -  "items",
        -  "totalCount"
        -]New value: +[
        +  "items",
        +  "appliedFilters",
        +  "totalCount"
        +]
    • Changedreliefweb_search_training2 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"
        +]
  9. 1 tool update
    • Changedreliefweb_list_sources1 field changed
      • 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."
  10. 6 tool updates
    • Changedreliefweb_list_countries1 field 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."
    • Changedreliefweb_list_sources1 field 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."
    • Changedreliefweb_search_disasters3 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"
        +}
    • Changedreliefweb_search_jobs3 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"
        +}
    • Changedreliefweb_search_reports3 fields changed
      • changedInput schema / properties / offset / description
        Previous value: -"Zero-based offset for pagination. Use with limit and totalCount from the response to page through large result sets."New value: +"Zero-based offset for pagination. Use with limit and the totalCount enrichment field to page through large result sets."
      • removedOutput schema / properties / message
        Removed value: -{
        -  "description": "Recovery hint when results are empty — echoes the filters applied and suggests how to broaden. Absent on successful result pages.",
        -  "type": "string"
        -}
      • addedOutput schema / properties / notice
        Added value: +{
        +  "description": "Recovery hint when results are empty — echoes the filters applied and suggests how to broaden. Absent on successful result pages.",
        +  "type": "string"
        +}
    • Changedreliefweb_search_training3 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"
        +}
  11. 9 tool updates
    • First observedreliefweb_get_country
    • First observedreliefweb_get_disaster
    • First observedreliefweb_get_report
    • First observedreliefweb_list_countries
    • First observedreliefweb_list_sources
    • First observedreliefweb_search_disasters
    • First observedreliefweb_search_jobs
    • First observedreliefweb_search_reports
    • First observedreliefweb_search_training

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.