mcp_iati_transaction_totals_by_country
Group aid commitments and disbursements by recipient country to get total amounts per country, with optional currency and row limit filters.
Instructions
Group commitments and disbursements by recipient country.
Amounts with different currencies and transaction types are reported
separately. Missing country names fall back to the country code, and
missing country data falls back to "Unknown recipient country".
Args:
transaction_type: Commitment or disbursement. Accepts commitment,
out commitment, disbursement, 2 or 3.
currency: Optional currency code, for example USD or EUR.
limit: Maximum number of grouped rows to return. Default: 50.
Returns:
A table containing the country code and name, transaction type,
currency and total amount.
Relevant IATI terms:
- 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.
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 |
|---|---|---|---|
| limit | No | ||
| currency | No | ||
| transaction_type | No | 2 |
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. |