mcp_iati_file_overview
Summarize the configured IATI file: total activities, reporting organizations, recipient countries, default currencies, and transaction totals by type and currency. Get an overview of aid data.
Instructions
Summarise the contents of the configured IATI file.
Use this tool for general questions such as what the file contains,
how many activities it has, which organisations report them, which
recipient countries and currencies appear, and how much financial
activity is reported.
Financial totals are kept separate by transaction type and currency.
The result includes:
- Total number of activities.
- Reporting organisations and their activity counts.
- Recipient countries and their activity counts.
- Default currencies used by activities.
- Transaction totals by type and currency.
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.
Reporting organisation: Organisation responsible for publishing and maintaining an activity's data; not necessarily the one funding or implementing the project.
Recipient country or region: Country (ISO code) or supra-national DAC region that receives the intended benefits of an activity. May include a percentage when the activity is split across several territories.
Transaction: Financial operation associated with an IATI activity, identified by its type, date, value and currency.
Transaction type: Code indicating the nature of a financial operation: incoming funds, commitment, disbursement, expenditure, interest payment, loan repayment, reimbursement, purchase or sale of equity, credit guarantee, incoming commitment, or outgoing/incoming pledge.
Transaction value: Amount of an individual transaction, expressed in the currency stated on the value or, if unspecified, in the activity's default currency.
Default currency: Currency declared for an activity and used whenever a financial value does not explicitly specify another currency.
Commitment: Financial obligation undertaken to provide funds to an activity; it does not necessarily represent a payment already made.
Disbursement: Transfer of funds from a provider organisation to a receiver organisation to finance an activity.
Expenditure: Use of funds to purchase goods or services related to an activity; not a synonym of disbursement.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output 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. |