Skip to main content
Glama
okfn
by okfn

mcp_iati_activity_summary

Retrieve the title, status, reporting organisation, and transaction type totals for an IATI activity using its identifier.

Instructions

Return the title, status, reporting organisation and totals per transaction type of an IATI activity.

    Args:
        iati_identifier: IATI identifier, for example "XI-IATI-IADB-BR-L1231".
            Obtained with search_activities.

    Relevant IATI terms:
    - 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.

  • Activity status: Stage of an activity within its lifecycle: pipeline/identification, implementation, completion, post-completion, cancelled or suspended.

  • Transaction: Financial operation associated with an IATI activity, identified by its type, date, value and 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.

  • Default currency: Currency declared for an activity and used whenever a financial value does not explicitly specify another currency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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?

With no annotations, the description carries the burden of behavioral disclosure. It clarifies semantic nuances, such as reporting organisation not necessarily being the funder and expenditure not being a synonym for disbursement, which helps avoid misinterpretation. However, it does not disclose error behavior, missing-activity handling, or data freshness, leaving notable gaps for an unannotated tool.

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 core purpose is front-loaded in the first sentence, and the glossary is organized by relevant IATI terms. The description is longer than strictly necessary, but each term supports correct use of the tool, especially around transaction types and financial terminology, so the length is mostly justified.

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 description provides enough domain context for a one-parameter tool: it explains key IATI concepts, gives an identifier example, and mentions that the identifier comes from search_activities. The output schema exists and likely documents return values, so the description does not need to restate them. Minor gaps around edge cases like missing activities prevent a higher score.

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?

The schema provides only the parameter name and type with 0% description coverage, but the description compensates well by giving a concrete example ('XI-IATI-IADB-BR-L1231') and explaining how to obtain the identifier via search_activities. This adds meaningful usage context beyond the bare schema.

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 uses a specific verb 'Return' and names the exact resource (IATI activity) and fields (title, status, reporting organisation, totals per transaction type). This clearly differentiates it from sibling tools like activity_transactions or transaction_totals_by_year, which target different data granularity.

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 implies the tool is for retrieving a summary of a single IATI activity and states that the identifier is obtained via search_activities. However, it does not explicitly say when to choose this tool over alternatives such as activity_transactions or transaction_totals_by_year, so usage guidance remains implied rather than explicit.

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