Skip to main content
Glama
okfn
by okfn

mcp_iati_transaction_totals_by_organisation

Group IATI aid transactions by reporting organisation to show total commitments and disbursements per transaction type, currency, and organisation.

Instructions

Group commitments and disbursements by reporting organisation.

    Amounts with different currencies and transaction types are reported
    separately. The reporting organisation publishes the activity data and
    is not necessarily the organisation funding or implementing the
    activity.

    Args:
        limit: Maximum number of grouped rows to return. Default: 50.

    Returns:
        A table containing the organisation reference and name,
        transaction type, currency and total amount.

    Relevant IATI terms:
    - Reporting organisation: Organisation responsible for publishing and maintaining an activity's data; not necessarily the one funding or implementing the project.
  • 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

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.
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does well by explaining that amounts with different currencies and transaction types are reported separately, that the reporting organisation is not necessarily the funder or implementer, and that the result is a table with organisation, transaction type, currency, and total amount. This goes beyond the tool name and adds meaningful context.

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 purpose, arguments, and return description are front-loaded and clearly separated. However, the extensive 'Relevant IATI terms' glossary is lengthy and contains generic domain definitions that are not necessary for calling this specific tool, making the description more bloated than needed.

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 tool with a single optional parameter and an output schema, the description covers the key semantics: grouping dimension, currency/type separation, output fields, and limit behavior. It is nearly complete; only minor details like output ordering or handling of empty results are absent.

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%, but the description compensates by fully documenting the only parameter: 'limit: Maximum number of grouped rows to return. Default: 50.' This adds meaning beyond the schema's bare 'Limit' title and is sufficient for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Group commitments and disbursements by reporting organisation.' This states exactly what the tool does and the output table is listed. It is clear, though it does not explicitly contrast with sibling aggregation tools like mcp_iati_transaction_totals_by_year, by_sector, or by_country.

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

Usage Guidelines2/5

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

The description provides no guidance about when to use this tool versus the many sibling tools (by year, by sector, by country, activity_transactions). There are no usage conditions, exclusions, or alternative recommendations. Users must infer the appropriate selection from the tool name alone.

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