Dbnomics

Search

search

Read-onlyIdempotent

Full-text search across all providers. Returns matching series with provider/dataset/series codes and human labels.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Results, 1-1000 (default 20)
`query`	Yes	Free-text search
`offset`	No	0-based offset

Output Schema

TableJSON Schema

Name	Required	Description	Default
`_meta`	No
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 20, 2026

addedOutput schema / properties / _meta

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

removedOutput schema / properties / limit

Removed value: -{
-  "description": "Number of results requested",
-  "type": "number"
-}

removedOutput schema / properties / offset

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

addedOutput schema / properties / results

Added value: +{
+  "properties": {
+    "docs": {
+      "items": {
+        "properties": {
+          "code": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "dir_hash": {
+            "type": "string"
+          },
+          "indexed_at": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "nb_matching_series": {
+            "type": "number"
+          },
+          "nb_series": {
+            "type": "number"
+          },
+          "provider_code": {
+            "type": "string"
+          },
+          "provider_name": {
+            "type": "string"
+          },
+          "updated_at": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "num_found": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / series

Removed value: -{
-  "description": "List of matching time series",
-  "items": {
-    "properties": {
-      "dataset_code": {
-        "description": "Dataset identifier",
-        "type": "string"
-      },
-      "provider_code": {
-        "description": "Provider identifier",
-        "type": "string"
-      },
-      "series_code": {
-        "description": "Series identifier",
-        "type": "string"
-      },
-      "series_name": {
-        "description": "Human-readable series name",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / total_count

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

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "unemployment rate"
+  },
+  {
+    "limit": 50,
+    "query": "GDP France"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "limit": {
+      "description": "Number of results requested",
+      "type": "number"
+    },
+    "offset": {
+      "description": "Offset of results",
+      "type": "number"
+    },
+    "series": {
+      "description": "List of matching time series",
+      "items": {
+        "properties": {
+          "dataset_code": {
+            "description": "Dataset identifier",
+            "type": "string"
+          },
+          "provider_code": {
+            "description": "Provider identifier",
+            "type": "string"
+          },
+          "series_code": {
+            "description": "Series identifier",
+            "type": "string"
+          },
+          "series_name": {
+            "description": "Human-readable series name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_count": {
+      "description": "Total matching series count",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds a small amount of behavioral context by noting the search spans all providers and returns series codes and labels, but it does not disclose deeper behavior such as ranking, relevance, or pagination beyond the schema.

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?

The description is two sentences with no filler. The core purpose and scope are front-loaded, and the return value summary earns its place without redundancy.

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?

Given the strong annotations, complete schema coverage, and presence of an output schema, the description is largely sufficient. The only meaningful gap is the lack of explicit guidance on when to use a sibling search tool instead, which slightly reduces completeness.

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%, including 'Free-text search', 'Results, 1-1000 (default 20)', and '0-based offset'. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific action ('Full-text search') and a clear resource scope ('across all providers'), then specifies what is returned ('matching series with provider/dataset/series codes and human labels'). This clearly distinguishes it from narrower siblings like search_within or find_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 clearly implies this is the tool for full-text search over all providers, which is useful contextual guidance. However, it does not explicitly mention when to prefer alternatives such as search_within or find_series, nor does it state exclusions for narrower searches.

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.