mcp_iati_transaction_totals_by_year
Group IATI commitments and disbursements by year and currency, filterable by year range, to produce a chronological table of totals per transaction type.
Instructions
Group commitments and disbursements by year and currency.
Only commitment and disbursement transactions are included. Amounts
with different currencies are always reported separately.
Args:
year_from: Optional first year to include.
year_to: Optional last year to include.
Returns:
A chronological table containing year, transaction type, currency
and total amount.
Relevant IATI terms:
- 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.
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.
Default currency: Currency declared for an activity and used whenever a financial value does not explicitly specify another currency.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| year_to | No | ||
| year_from | No |
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. |