Skip to main content
Glama
Sign In

Oecd

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Curated Flows

list_curated_flows
Read-onlyIdempotent

List OECD dataflow refs we have pre-vetted, grouped by topic (gdp, labour, prices, finance, households, health, demographics, projections, tax, education, environment, technology). Pass the flow_ref to fetch_dataset. For everything else use search_dataflows or browse https://data-explorer.oecd.org.

Input Schema

NameRequiredDescriptionDefault
topicNoOptional topic filter

Output Schema

NameRequiredDescriptionDefault
noteYesReference to additional data sources
countYesNumber of flows in result
flowsYesCurated dataflow definitions
topicsYesAvailable topics across all curated flows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "topic": "gdp"
+  },
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of flows in result",
+      "type": "number"
+    },
+    "flows": {
+      "description": "Curated dataflow definitions",
+      "items": {
+        "properties": {
+          "flow_ref": {
+            "description": "SDMX dataflow reference identifier",
+            "type": "string"
+          },
+          "notes": {
+            "description": "Optional additional notes",
+            "type": "string"
+          },
+          "title": {
+            "description": "Human-readable dataflow title",
+            "type": "string"
+          },
+          "topic": {
+            "description": "Topic category (gdp, labour, prices, etc.)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "flow_ref",
+          "topic",
+          "title"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "description": "Reference to additional data sources",
+      "type": "string"
+    },
+    "topics": {
+      "description": "Available topics across all curated flows",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "topics",
+    "flows",
+    "note"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds context that the data is pre-vetted and grouped by topic, which is useful behavioral info beyond what annotations provide. No contradictions.

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 that front-load purpose and include guidance. No unnecessary 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?

Given the presence of an output schema and rich annotations, the description sufficiently explains what the tool returns (grouped refs), how to use the output (with fetch_dataset), and when to use alternatives. 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?

The schema covers the single parameter 'topic' with a description, but the description enriches it by listing example values (gdp, labour, etc.), which are not in the schema (no enums). This helps the agent understand valid inputs.

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'), the resource ('OECD dataflow refs we have pre-vetted'), and the organization ('grouped by topic'). It also distinguishes from sibling tools like search_dataflows and fetch_dataset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool (for pre-vetted flows) and when to use alternatives ('For everything else use search_dataflows or browse...'). Also provides next steps: 'Pass the flow_ref to fetch_dataset.'

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

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

Resources