Skip to main content
Glama
okfn
by okfn

mcp_iati_top_activities_by_amount

Find IATI activities with the highest commitment or disbursement totals. Rank results per currency, with optional currency and limit filters to target specific aid flows.

Instructions

List activities with the highest commitment or disbursement totals.

    Rankings are calculated independently for each currency, avoiding
    comparisons between amounts expressed in different currencies.

    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 results to return per currency. Default: 10.

    Returns:
        A table containing activity identifiers, titles, reporting
        organisations, recipient countries, transaction type, currency
        and total amount.

    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.
  • IATI identifier: Globally unique code identifying an IATI activity, also used to link it to its transactions and other information.

  • 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.

  • 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

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
currencyNo
transaction_typeNo2

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoPlain text message that bypasses LLM processing and should be printed exactly as provided in the user interface.
tableNoTwo-dimensional list (list of rows) representing tabular data, e.g., from CSV or TSV sources. Each row should be a list of cell values.
chartsNoList of dictionaries containing data and configuration for rendering a Chart.js chart in the chat interface.
sourcesYesURL(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.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that rankings are calculated independently per currency to avoid cross-currency comparisons, and it lists the return fields. However, it does not disclose potential edge cases, performance behavior, default currency handling when currency is null, or error conditions. It explains the expected behavior but is not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core description is concise and front-loaded with the main purpose and key behavior. However, the appended glossary of IATI terms is lengthy and generic, not tool-specific. While informative, it inflates the description size significantly and could be truncated or moved to documentation. The Args/Returns structure is clear, but overall conciseness suffers from the glossary overload.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so return values are covered externally. The description explains the parameters sufficiently and the glossary provides background on IATI concepts. Given the tool's simplicity (three optional parameters) and the existence of the output schema, the description gives enough for an agent to call it correctly. The only gap is explicit usage guidance versus siblings, but that is a separate dimension.

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 description coverage is 0%, so the description must compensate. It does so effectively: transaction_type lists acceptable values ('commitment, out commitment, disbursement, 2 or 3'), currency gives examples ('USD or EUR'), and limit specifies 'Maximum results to return per currency. Default: 10.' This adds meaning beyond the raw schema types, though it leaves some conceptual details (e.g., the meaning of 'out commitment') to the glossary.

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 and resource: 'List activities with the highest commitment or disbursement totals.' It also clarifies the per-currency ranking logic, which distinguishes it from sibling tools like transaction_totals_by_* that aggregate totals. This is a clear, unambiguous purpose that would let an agent pick this tool without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but does not explicitly state when to use it versus alternatives. It mentions the ranking per currency and parameters, but there is no direct guidance on when to prefer this over e.g. mcp_iati_transaction_totals_by_country or mcp_iati_activity_transactions. Usage is implied from the purpose, but no exclusions or alternative conditions are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/okfn/mcp-iati'

If you have feedback or need assistance with the MCP directory API, please join our Discord server