mcp_iati_date_coverage
Check the date range covered by IATI data, selecting activity, transaction, or both date kinds, and get earliest/latest valid dates with counts of valid, missing, or invalid records.
Instructions
Report the date range covered by the configured IATI data.
Use date_kind to select activity dates, transaction dates or both:
- activities: planned and actual start and end dates.
- transactions: dates of financial transactions.
- all: both activity and transaction dates.
The result reports the earliest and latest valid date together with
counts of records containing valid, missing or invalid dates.
Relevant IATI terms:
- IATI activity: A development or cooperation intervention published under the IATI standard; it can represent a project, a programme or another unit of work.
Activity date: Start or end date of an activity. Each date declares one of four types: planned start, actual start, planned end or actual end.
Transaction: Financial operation associated with an IATI activity, identified by its type, date, value and currency.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date_kind | No | all |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| force | No | Plain text message that bypasses LLM processing and should be printed exactly as provided in the user interface. | |
| table | No | Two-dimensional list (list of rows) representing tabular data, e.g., from CSV or TSV sources. Each row should be a list of cell values. | |
| charts | No | List of dictionaries containing data and configuration for rendering a Chart.js chart in the chat interface. | |
| sources | Yes | URL(s) that users can nagivate to to download the data used for the analysis. E.g., landing page, feed, file endpoint, CKAN resource page, etc. |