IMF DataMapper Series

search_indicators

Searches the IMF DataMapper indicator catalog by keyword over code, label and description (e.g. inflation, debt, unemployment). Returns indicator code, label, unit, dataset and description to pass to get_series. Empty query lists the first matches.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_indicators"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum indicators to return, 1-100
`query`	No	Keyword(s); all words must match. Empty lists indicators
`dataset`	No	Optional dataset code filter, e.g. WEO

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses useful details: the search fields, example keywords, return fields, and empty-query behavior. It does not cover auth or rate limits, but it gives enough operational context for a read-only catalog search.

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

Conciseness5/5

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

The description is compact and front-loaded, with the core search behavior stated first and the downstream get_series use stated second. Every sentence contributes useful information without repetition.

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?

Because there is no output schema, the description responsibly lists the returned indicator fields and explains the empty-query case. It is largely complete for a three-parameter search tool, though it does not describe response ordering or pagination beyond the limit parameter.

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 coverage is 100%, so the baseline is 3. The description still adds value by clarifying that the query matches over code, label, and description and by giving representative keyword examples.

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: searches the IMF DataMapper indicator catalog by keyword over code, label, and description. It also distinguishes the tool from its sibling by saying the returned fields are meant to be passed to get_series.

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 makes the usage context clear: this tool is for discovering indicator codes to pass to get_series. It also explains the empty-query fallback, though it does not explicitly say when not to use this tool versus alternatives.

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

All IMF DataMapper Series tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?