Skip to main content
Glama

IMF (Unofficial)

Search Indicators

search_indicators
Read-onlyIdempotent

Discover what a dataset accepts: its dimension names in key order, and the codes available for each, filtered by query. Use this before get_data, e.g. search_indicators({dataset:"CPI", query:"united states"}) finds COUNTRY=USA. Without a query it returns the dimension list and a sample of codes.

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": {
      "query": "united states",
      "dataset": "CPI"
    },
    "name": "search_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional term matched against code ids and names, e.g. "united states", "GDP", "monthly".
datasetYesDataset id from get_datasets, e.g. "CPI".

Output Schema

NameRequiredDescriptionDefault
nameNo
queryNoLowercase search query term used for filtering
datasetNo
structureNoIMF DataStructure containing indicator code dimensions and metadata
dimensionsNo
dimension_orderNo
unmatched_codelistsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / properties / dataset
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / dimension_order
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / dimensions
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "codelist": {
      +        "type": "string"
      +      },
      +      "codes": {
      +        "items": {
      +          "properties": {
      +            "code": {
      +              "type": "string"
      +            },
      +            "name": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "dimension": {
      +        "type": "string"
      +      },
      +      "matching_codes": {
      +        "type": "number"
      +      },
      +      "total_codes": {
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / unmatched_codelists
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "codelist": {
      +        "type": "string"
      +      },
      +      "codes": {
      +        "items": {
      +          "properties": {
      +            "code": {
      +              "type": "string"
      +            },
      +            "name": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "structure"
      -]
  2. Changed5 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "database_id": "IFS",
      -    "query": "GDP"
      -  },
      -  {
      -    "database_id": "BOP"
      -  }
      -]New value: +[
      +  {
      +    "dataset": "CPI",
      +    "query": "united states"
      +  },
      +  {
      +    "dataset": "CPI"
      +  }
      +]
    • removedInput schema / properties / database_id
      Removed value: -{
      -  "description": "IMF database ID to search within, e.g. \"IFS\"",
      -  "type": "string"
      -}
    • addedInput schema / properties / dataset
      Added value: +{
      +  "description": "Dataset id from get_datasets, e.g. \"CPI\".",
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Optional search term to filter indicators, e.g. \"GDP\", \"inflation\", \"trade\""New value: +"Optional term matched against code ids and names, e.g. \"united states\", \"GDP\", \"monthly\"."
    • changedInput schema / required
      Previous value: -[
      -  "database_id"
      -]New value: +[
      +  "dataset"
      +]
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavioral context: results are filtered by query, dimension ordering is preserved in key order, and the no-query path degrades to a sampled code list rather than an error.

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?

Three tight sentences: purpose and return shape first, then the workflow pointer, then the no-query fallback, anchored by an inline example. Nothing is redundant and the most important information is front-loaded.

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?

For a two-parameter read tool with full annotation coverage and an output schema, the description covers purpose, ordering semantics, query behavior, and the no-query case. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description adds meaning beyond the schema: it explains that omitting query changes the return shape (dimension list + sample) and that query matches against both ids and names. That downstream consequence is not captured by the parameter 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?

States a specific verb and resource ('Discover what a dataset accepts') and precisely what it returns: dimension names in key order plus available codes, filtered by query. The concrete example (search_indicators({dataset:"CPI", query:"united states"}) finds COUNTRY=USA) makes the tool's function unmistakable and distinguishes it from get_data.

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

Usage Guidelines5/5

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

Explicitly positions the tool in a workflow ('Use this before get_data') and explains the branch behavior: with a query it matches codes, without a query it returns the dimension list and a sample of codes. The agent knows both when to reach for it and what to expect from each invocation mode.

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.