Dbnomics

List Datasets

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.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	1-1000 (default 100)
`offset`	No	0-based offset
`provider`	Yes	Provider code (e.g. "ECB", "BLS", "EUROSTAT")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`_meta`	No
`provider`	No
`category_tree`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 20, 2026

addedOutput schema / properties / _meta

Added value: +{
+  "properties": {
+    "args": {
+      "properties": {
+        "provider_code": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / category_tree

Added value: +{
+  "items": {
+    "properties": {
+      "children": {
+        "items": {
+          "properties": {
+            "code": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "code": {
+        "type": [
+          "null",
+          "string"
+        ]
+      },
+      "doc_href": {
+        "type": "null"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / datasets

Removed value: -{
-  "description": "Available datasets for provider",
-  "items": {
-    "properties": {
-      "code": {
-        "description": "Dataset code",
-        "type": "string"
-      },
-      "last_update": {
-        "description": "Last update timestamp",
-        "type": "string"
-      },
-      "name": {
-        "description": "Dataset name",
-        "type": "string"
-      },
-      "series_count": {
-        "description": "Number of series",
-        "type": "number"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / limit

Removed value: -{
-  "description": "Limit applied",
-  "type": "number"
-}

removedOutput schema / properties / offset

Removed value: -{
-  "description": "Offset applied",
-  "type": "number"
-}

addedOutput schema / properties / provider

Added value: +{
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "indexed_at": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "region": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "terms_of_use": {
+      "type": "string"
+    },
+    "website": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / total_count

Removed value: -{
-  "description": "Total dataset count",
-  "type": "number"
-}

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "provider": "ECB"
+  },
+  {
+    "limit": 50,
+    "provider": "BLS"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "datasets": {
+      "description": "Available datasets for provider",
+      "items": {
+        "properties": {
+          "code": {
+            "description": "Dataset code",
+            "type": "string"
+          },
+          "last_update": {
+            "description": "Last update timestamp",
+            "type": "string"
+          },
+          "name": {
+            "description": "Dataset name",
+            "type": "string"
+          },
+          "series_count": {
+            "description": "Number of series",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "description": "Limit applied",
+      "type": "number"
+    },
+    "offset": {
+      "description": "Offset applied",
+      "type": "number"
+    },
+    "total_count": {
+      "description": "Total dataset count",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With readOnlyHint, openWorldHint, and idempotentHint already provided by annotations, the description adds useful behavioral detail: it returns code/name/dimension metadata and is paged with limit/offset. No contradiction with annotations.

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 sentences carry purpose, output behavior, paging, and downstream linkage with no filler. The most identifying information is front-loaded before examples.

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?

With an output schema and safety annotations present, the description covers the required provider, paging behavior, return fields, and downstream consumers. Nothing essential to selecting or invoking the tool is missing.

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%, so parameters are already documented. The description adds no new parameter-level detail beyond mentioning limit/offset paging and provider-code examples, which the schema already includes.

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 enumerates concrete provider examples. It further distinguishes the tool's output (dataset codes) from what downstream tools get_series and find_series expect.

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 clearly states the tool answers which datasets a provider publishes and that the returned codes feed get_series/find_series, implying when to call it. It does not explicitly name list_providers as an alternative for provider-level queries or state when not to use it.

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

All Dbnomics 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.