Skip to main content
Glama
icen-ai
by icen-ai

IMF DataMapper Query

ext_imf
Read-onlyIdempotent

Query IMF World Economic Outlook data for GDP growth, inflation, unemployment, current account, government debt, and more. Retrieve data for multiple indicators, countries, and time periods. Free and requires no authentication.

Instructions

查询 IMF 世界经济展望 (WEO) 数据。支持 GDP 增速、通胀、失业率、经常账户、政府债务等。支持同时查询多个指标。完全免费,无需认证。

Args:

  • indicators (string | string[]): 单个或多个指标名/IMF代码,如 "GDP_GROWTH" 或 ["GDP_GROWTH","CPI_INFLATION","GOVT_DEBT"]

  • countries (string[]): ISO 代码数组,如 ["CHN","USA","JPN"];默认 ["CHN"]

  • periods (string[]): 年份数组,如 ["2020","2021","2022","2023"];不传则返回全部

常用指标: GDP_GROWTH | GDP_USD | GDP_PER_CAPITA | CPI_INFLATION | UNEMPLOYMENT | CURRENT_ACCOUNT | GOVT_DEBT | GOVT_BALANCE | GROSS_SAVINGS | INVESTMENT | POPULATION

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indicatorsYes单个或多个指标名,如 "GDP_GROWTH" 或 ["GDP_GROWTH","CPI_INFLATION"]
countriesNoISO 代码数组,如 ["CHN","USA"]
periodsNo年份数组,如 ["2020","2021","2022"]
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds value by stating '完全免费,无需认证' (completely free, no authentication), which is behavioral context beyond annotations. No contradiction detected.

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 concise, with a front-loaded purpose statement and structured 'Args:' section. Every sentence is informative, and there is no redundant information. It efficiently uses both Chinese and English to cover key points.

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

Completeness3/5

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

Given the absence of an output schema, the description does not explain the return format or structure of the query results. While the input parameters and behavior are well-covered, the lack of output details leaves the agent uncertain about what to expect from the response.

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 100% schema description coverage, the description still adds significant value by providing usage examples (e.g., '["GDP_GROWTH","CPI_INFLATION"]') and a comprehensive list of common indicators. This helps the agent select valid parameter values beyond the schema's generic descriptions.

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 explicitly states it queries IMF World Economic Outlook (WEO) data and lists specific supported indicators. The verb '查询' (query) and resource 'IMF 世界经济展望 (WEO) 数据' are clear. It differentiates from siblings like ext_fred or ext_world_bank by specifying the IMF source, though not explicitly distinguishing from other IMF tools.

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 provides context (free, no auth, supports multiple indicators) but does not explicitly state when to use this tool over alternatives like ext_fred or ext_world_bank. Usage is implied for IMF data queries, but no exclusions or when-not-to-use guidance is given.

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/icen-ai/mcp-cnbs'

If you have feedback or need assistance with the MCP directory API, please join our Discord server