Skip to main content
Glama

Dbnomics List Datasets

dbnomics_list_datasets
Read-onlyIdempotent

DBnomics economic time-series aggregator, enumerate the datasets published by one DBnomics provider code (ECB, BLS, EUROSTAT, IMF, OECD, WB and 80+ national statistics agencies). Returns each dataset's code, name and dimension metadata, paged with limit/offset; those codes are what get_series and find_series expect. Answers which statistical datasets the ECB, IMF or Eurostat publish on DBnomics.

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": {
      "provider": "ECB"
    },
    "name": "dbnomics_list_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-1000 (default 100)
offsetNo0-based offset
providerYesProvider code (e.g. "ECB", "BLS", "EUROSTAT")

Output Schema

NameRequiredDescriptionDefault
_metaNo
providerNo
category_treeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds useful detail beyond them: results include code, name and dimension metadata, and the listing is paged via limit/offset. It does not mention rate limits, authentication, or failure modes for invalid provider codes.

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?

Three sentences, front-loaded with the core action and provider enumeration, then pagination, then downstream linkage. Dense but each clause carries information; the parenthetical provider list is long but functional.

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?

For a three-parameter read-only listing tool with an output schema and full annotation coverage, the description covers purpose, provider scope, paging, and how returned codes feed other tools. Only the linkage from provider discovery (dbnomics_list_providers) is unstated, a minor gap.

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 description coverage is 100%, so baseline is 3. The description reinforces that 'provider' is a DBnomics provider code and that limit/offset control paging, but adds no format, default, or boundary information beyond what the schema already documents.

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 opens with a specific verb and resource: 'enumerate the datasets published by one DBnomics provider code,' and lists example providers (ECB, BLS, EUROSTAT, IMF, OECD, WB) to remove ambiguity about what a 'provider' is. It also distinguishes the resource from sibling operations by naming get_series and find_series as downstream consumers of the returned codes.

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?

It gives clear context for when to use it: to discover which datasets a provider publishes, and as the step before calling get_series or find_series. It does not explicitly name the companion tool dbnomics_list_providers as the way to obtain a valid provider code, nor state exclusions, so it stops short of full when/when-not guidance.

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.