Oecd

Search Dataflows

search_dataflows

Read-onlyIdempotent

Search OECD's SDMX dataflow registry by keyword. Returns matching dataflow refs ready to pass to fetch_dataset. If results are noisy, refine with a more specific keyword or restrict by agency.

Input Schema

Name	Required	Description
`limit`	No	Max results (default 25, max 100)
`query`	Yes	Keyword (matches dataflow names + descriptions)
`agency`	No	Optional agency filter, e.g., OECD.SDD.NAD, OECD.ECO, OECD.ENV

Output Schema

Name	Required	Description
`returned`	Yes	Number of results returned (capped by limit)
`dataflows`	Yes	Matching dataflows
`total_matched`	Yes	Total number of dataflows matching query

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "unemployment rate"
+  },
+  {
+    "agency": "OECD.ELS",
+    "limit": 10,
+    "query": "health expenditure"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "dataflows": {
+      "description": "Matching dataflows",
+      "items": {
+        "properties": {
+          "agency": {
+            "description": "Agency identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "flow_ref": {
+            "description": "Complete SDMX dataflow reference",
+            "type": "string"
+          },
+          "id": {
+            "description": "Dataflow ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Dataflow name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "version": {
+            "description": "Dataflow version",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "flow_ref",
+          "agency",
+          "id",
+          "version",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of results returned (capped by limit)",
+      "type": "number"
+    },
+    "total_matched": {
+      "description": "Total number of dataflows matching query",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_matched",
+    "returned",
+    "dataflows"
+  ],
+  "type": "object"
+}

First observedMay 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds value by stating output nature (dataflow refs) and next-step usage, without contradicting 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?

Two concise sentences: first defines purpose and outcome, second provides refinement advice. No wasted words.

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?

Simple tool with clear purpose, good annotations, and output schema. Description covers purpose, usage, and output relation completely for its complexity.

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 clear explanations for each parameter. The description does not add significant new meaning beyond 'restrict by agency' which is implied in schema.

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?

Clearly states verb 'Search', resource 'OECD SDMX dataflow registry', and outcome 'Returns matching dataflow refs ready to pass to fetch_dataset'. Distinguishes from sibling fetch_dataset by indicating workflow relationship.

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?

Provides explicit guidance: 'If results are noisy, refine with a more specific keyword or restrict by agency.' Also implies usage before fetch_dataset. No explicit when-not, but context is clear.

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

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