Skip to main content
Glama

IMF (Unofficial)

Get Datasets

get_datasets
Read-onlyIdempotent

List or search the IMF's datasets, CPI, WEO (World Economic Outlook), BOP (Balance of Payments), IMTS (trade in goods), GFS (government finance), MFS (monetary and financial), FSI (financial soundness), commodity prices and ~200 more. Returns the dataset id to pass to get_data and search_indicators, plus its name and description. Pass query to filter by name, e.g. "inflation", "trade", "government".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax datasets to return, 1-250 (default 50).
queryNoOptional filter matched against dataset id, name and description (e.g. "inflation", "trade").

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {}
      -]New value: +[
      +  {},
      +  {
      +    "limit": 50,
      +    "query": "price"
      +  }
      +]
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Max datasets to return, 1-250 (default 50).",
      +  "type": "number"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Optional filter matched against dataset id, name and description (e.g. \"inflation\", \"trade\").",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real value beyond that: it discloses the shape of the result (dataset id plus name and description) and the downstream chaining contract with get_data and search_indicators. It omits anything about pagination behavior or result ordering, which keeps it below a 5.

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?

Front-loaded with the verb and resource, then the downstream contract, then the query hint — a sensible order with no filler sentences. The long parenthetical enumeration of acronyms (BOP, IMTS, GFS, MFS, FSI) is dense but earns its place by signalling coverage to an agent deciding whether the IMF source is relevant.

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 (two optional params, output schema present, rich annotations), and the description covers everything an agent needs: what it searches, what it returns, and how to use the returned id. Return values need not be spelled out further because an output schema exists, and the description nonetheless highlights the one field that matters for chaining.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with both `limit` (range and default) and `query` (match fields, examples) fully documented in the schema, so baseline 3 applies. The description only repeats the filter idea for `query` and adds one example term ("government") that is not in the schema; it adds no matching semantics such as case sensitivity or partial-match behavior.

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?

States a specific verb and resource ("List or search the IMF's datasets") and enumerates the dataset families covered (CPI, WEO, BOP, IMTS, GFS, MFS, FSI, commodity prices, ~200 more), so an agent knows the exact scope. It also differentiates itself implicitly by framing the tool as a discovery step that yields ids for get_data and search_indicators.

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?

Clearly positions the tool as the prerequisite discovery step: "Returns the dataset id to pass to get_data and search_indicators," which tells an agent when to call this instead of going straight to a data fetch. It gives concrete query examples ("inflation", "trade", "government") but no explicit when-not guidance or statement of what to do if the query returns nothing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.