Skip to main content
Glama
Sign In
OECD MCP Server

OECD MCP Server

by isakskogstad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_dataflows

Browse OECD datasets by topic area. Filter available dataflows by category to find relevant economic, health, education, and other datasets.

Instructions

List available OECD dataflows (datasets), optionally filtered by category. Use this to browse datasets by topic area.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_dataflows"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional category filter: ECO, HEA, EDU, ENV, TRD, JOB, NRG, AGR, GOV, SOC, DEV, STI, TAX, FIN, TRA, IND, REG, HOU, MIG
limitNoMaximum number of results (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states basic list/filter functionality. It does not disclose behavioral traits such as pagination, sorting, rate limits, or what happens with no results. Minimal disclosure.

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 purpose and optional filter are stated upfront, making it easy to parse.

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?

For a simple list tool with two optional parameters and no output schema, the description is fairly complete. It provides enough context for browsing, though it could mention the return format (e.g., list of names/IDs).

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 coverage is 100%, and the description adds marginal meaning by linking category filtering to browsing by topic area. However, it does not provide new syntax or format details beyond the schema, so baseline score 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 clearly states the verb 'List' and resource 'OECD dataflows (datasets)', and clarifies optional filtering by category. It effectively distinguishes from siblings like 'get_categories' and 'search_dataflows' by focusing on browsing datasets by topic area.

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

Usage Guidelines3/5

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

The description implies usage for browsing datasets by topic area but does not provide explicit guidance on when to use this tool versus alternatives like 'search_dataflows' or conditions to avoid. No exclusion criteria or alternative recommendations are given.

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

Deploy Server

Other Tools