Dbnomics

Find Series

find_series

Read-onlyIdempotent

Browse series with structured filters. Useful when you know the provider+dataset and want to enumerate series by dimensions. If a filter matches nothing, the response lists the dimension codes the dataset actually accepts.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	1-1000 (default 100)
`offset`	No	0-based offset
`dataset`	Yes	Dataset code
`provider`	Yes	Provider code
`dimensions`	No	Optional dimension filter map. A value may be one code or a list of codes to OR together, e.g. {"FREQ":"M"} or {"FREQ":["M","Q"],"CURRENCY":["USD","GBP"]}.
`observations`	No	Include observations (default false to save bandwidth)

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Limit applied
`offset`	No	Offset applied
`series`	No	Series matching dimension filters
`total_count`	No	Total series count

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 31, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "dataset": "EXR",
-    "dimensions": {
-      "FREQ": "M"
-    },
-    "provider": "ECB"
-  },
-  {
-    "dataset": "UNE_RT_A",
-    "dimensions": {
-      "COUNTRY": "DE",
-      "SEX": "T"
-    },
-    "observations": true,
-    "provider": "EUROSTAT"
-  }
-]New value: +[
+  {
+    "dataset": "EXR",
+    "dimensions": {
+      "FREQ": "M"
+    },
+    "provider": "ECB"
+  },
+  {
+    "dataset": "une_rt_a",
+    "dimensions": {
+      "geo": "DE",
+      "sex": "T"
+    },
+    "limit": 3,
+    "provider": "EUROSTAT"
+  }
+]

addedInput schema / properties / dimensions / additionalProperties / oneOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / dimensions / additionalProperties / type
```
Removed value: -"string"
```

changedInput schema / properties / dimensions / description

Previous value: -"Optional dimension filter map, e.g. {\"FREQ\":\"A\",\"COUNTRY\":\"DE\"}"New value: +"Optional dimension filter map. A value may be one code or a list of codes to OR together, e.g. {\"FREQ\":\"M\"} or {\"FREQ\":[\"M\",\"Q\"],\"CURRENCY\":[\"USD\",\"GBP\"]}."

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "dataset": "EXR",
+    "dimensions": {
+      "FREQ": "M"
+    },
+    "provider": "ECB"
+  },
+  {
+    "dataset": "UNE_RT_A",
+    "dimensions": {
+      "COUNTRY": "DE",
+      "SEX": "T"
+    },
+    "observations": true,
+    "provider": "EUROSTAT"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "limit": {
+      "description": "Limit applied",
+      "type": "number"
+    },
+    "offset": {
+      "description": "Offset applied",
+      "type": "number"
+    },
+    "series": {
+      "description": "Series matching dimension filters",
+      "items": {
+        "properties": {
+          "dimensions": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "description": "Dimension values for series",
+            "type": "object"
+          },
+          "name": {
+            "description": "Series name",
+            "type": "string"
+          },
+          "observations": {
+            "description": "Time series data points (if requested)",
+            "items": {
+              "properties": {
+                "date": {
+                  "description": "Observation date",
+                  "type": "string"
+                },
+                "value": {
+                  "description": "Observed value or null",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "series_code": {
+            "description": "Series code",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_count": {
+      "description": "Total series count",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description doesn't need to repeat that. It adds a genuinely useful behavioral detail: 'If a filter matches nothing, the response lists the dimension codes the dataset actually accepts.' This aids error handling and goes beyond what annotations provide.

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, front-loaded with the core purpose and followed by a concise usage context and a relevant edge-case behavior. Every sentence earns its place with no redundant or filler content.

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 tool's 6 parameters, nested objects, and presence of an output schema, the description is concise but sufficient. It covers the primary use case and a key behavioral nuance, while the schema and annotations fill in parameter and safety details. It doesn't cover pagination or observations, but those are clearly documented in the schema, so completeness is adequate.

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%, with detailed explanations for each parameter, including the dimensions filter semantics and the observations flag. The description adds only conceptual context ('structured filters', 'provider+dataset') without introducing new parameter-level meaning. Thus, the baseline 3 is appropriate as the schema does the heavy lifting.

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 ('browse series') with a clear resource ('series') and mechanism ('structured filters'). It further clarifies the use case of enumerating series by dimensions for a given provider and dataset, which distinguishes it from related tools like get_series (which likely retrieves a single series) and list_datasets/list_providers.

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 phrase 'Useful when you know the provider+dataset' explicitly indicates the prerequisite context for use. It does not name alternatives or state exclusions, but the implied contrast with tools that discover datasets/providers gives clear guidance. A minor gap is the lack of explicit 'when not to use' scenarios.

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.