Skip to main content
Glama
okfn
by okfn

mcp_iati_search_activities

Search IATI activities by title text to find their unique IATI identifier, then use it to get detailed activity summaries.

Instructions

Search IATI activities whose title contains the given text.

    Useful as a first step to discover an activity's IATI identifier,
    before requesting its summary with activity_summary.

    Args:
        text: Substring to search for in the title (case-insensitive).
        limit: Maximum number of results to return. Default: 10.

    Returns:
        A table with the IATI identifier, title and status of each match.

    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.

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

Input Schema

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the match is a case-insensitive substring search, that limit controls maximum results, and that the response is a table containing identifier, title, and status. This is transparent enough for a simple read-style search tool, though edge cases like empty results are not mentioned.

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 well-structured with clear Args/Returns sections and front-loads the main purpose. The 'Relevant IATI terms' block is somewhat verbose but provides useful domain context for an AI agent and does not overshadow the essential usage information.

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

Completeness5/5

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

The tool is simple, has only two parameters, and an output schema is already present. The description covers the use case, parameter semantics, result contents, and domain terminology, so an agent has everything needed to select and call this tool correctly.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters: text is a case-insensitive substring to search for in the title, and limit is the maximum number of results with a default of 10. This adds real meaning beyond the bare schema types.

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 clearly states the tool 'Search IATI activities whose title contains the given text', naming a specific verb, resource, and matching mechanism. It also positions itself as a first step toward discovering an IATI identifier, which helps distinguish it from the sibling activity_summary tool.

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

Usage Guidelines4/5

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

The description explicitly says it is useful as a first step to discover an activity's IATI identifier before requesting its summary with activity_summary. This gives a clear when-to-use signal and names a relevant sibling, though it does not enumerate exclusions for other sibling tools.

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