Skip to main content
Glama
okfn
by okfn

mcp_iati_activity_transactions

Retrieve financial transactions linked to an IATI activity. Get chronological details including type, value, currency, and description for analysis.

Instructions

List the transactions associated with an IATI activity.

    Transactions are returned in chronological order and include their
    type, value, currency and published description.

    Args:
        iati_identifier: IATI identifier of the activity.
        limit: Maximum number of transactions to return. Default: 50.

    Returns:
        A table containing the transactions associated with the
        requested activity.

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

  • Expenditure: Use of funds to purchase goods or services related to an activity; not a synonym of disbursement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
iati_identifierYes

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 usefully discloses chronological ordering and the included transaction fields, and 'List' implies a read-only operation. However, it does not address error behavior, pagination beyond the limit parameter, authentication requirements, or what happens when an invalid iati_identifier is supplied.

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

Conciseness4/5

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

The description is front-loaded with its purpose and follows a clear Args/Returns structure. The 'Relevant IATI terms' section is useful domain context but somewhat lengthy; not every definition is strictly required to invoke the tool correctly.

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?

For a simple two-parameter list operation with an output schema, the description covers the tool's purpose, parameters, return ordering, included fields, and relevant domain terminology. Minor gaps include explicit alternative routing and edge-case or error behaviour, but these are not critical at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully documents both parameters: iati_identifier is described as the IATI identifier of the activity, and limit is described as the maximum number of transactions to return with its default of 50. The glossary also reinforces the meaning of an IATI identifier.

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 opens with 'List the transactions associated with an IATI activity', which is a specific verb plus resource. It further specifies what the returned transactions include (type, value, currency, published description), clearly distinguishing it from sibling aggregation tools like mcp_iati_transaction_totals_by_year.

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 use case is implied: this tool returns individual transactions in chronological order, while sibling tools compute transaction totals by year, organisation, sector, or country. However, there is no explicit statement of when to choose this tool over alternatives or any exclusions, so the agent must infer the distinction.

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