Dbnomics

List Providers

list_providers

Read-onlyIdempotent

List all statistics providers available in DBnomics (80+), including provider codes (e.g. ECB, BLS, EUROSTAT, IMF, OECD) and their names. Use provider codes with list_datasets and get_series.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`_meta`	No
`nb_series`	No
`providers`	No	Available statistics providers
`nb_datasets`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedJun 2, 2026

addedOutput schema / properties / _meta

Added value: +{
+  "properties": {
+    "args": {
+      "properties": {
+        "limit": {
+          "type": "number"
+        },
+        "offset": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / nb_datasets
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / nb_series
```
Added value: +{
+  "type": "number"
+}
```

removedOutput schema / properties / providers / items

Removed value: -{
-  "properties": {
-    "code": {
-      "description": "Provider code",
-      "type": "string"
-    },
-    "datasets_count": {
-      "description": "Number of datasets",
-      "type": "number"
-    },
-    "name": {
-      "description": "Provider name",
-      "type": "string"
-    },
-    "region": {
-      "description": "Geographic region",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

addedOutput schema / properties / providers / properties

Added value: +{
+  "docs": {
+    "items": {
+      "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"
+    },
+    "type": "array"
+  },
+  "limit": {
+    "type": "number"
+  },
+  "num_found": {
+    "type": "number"
+  },
+  "offset": {
+    "type": "number"
+  }
+}

changedOutput schema / properties / providers / type
```
Previous value: -"array"New value: +"object"
```

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "providers": {
+      "description": "Available statistics providers",
+      "items": {
+        "properties": {
+          "code": {
+            "description": "Provider code",
+            "type": "string"
+          },
+          "datasets_count": {
+            "description": "Number of datasets",
+            "type": "number"
+          },
+          "name": {
+            "description": "Provider name",
+            "type": "string"
+          },
+          "region": {
+            "description": "Geographic region",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds context by stating the approximate count (80+) and what data is returned (codes and names), which aligns with annotations and adds value beyond them.

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?

Two sentences with no wasted words. The first sentence states the core action and scope; the second provides usage guidance. Front-loaded and concise.

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?

Given the tool has no parameters and an output schema exists, the description is complete. It covers the tool's output and how to use it with siblings. No gaps.

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?

With zero parameters, the baseline is 4. The description does not need to add parameter details, but it does mention the output content (provider codes and names), which indirectly clarifies what the tool provides.

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 clearly states the action ('List all statistics providers'), specifies the resource ('DBnomics'), and notes the content (codes and names). It also hints at linkage with sibling tools, but the core purpose is distinct from tools like list_datasets or get_series.

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 explicitly states to use provider codes with list_datasets and get_series, guiding the agent on downstream usage. It does not explicitly say when not to use, but the simplicity of the tool (no parameters) makes that unnecessary.

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.