CNBS MCP Server

List OECD Datasets

ext_oecd_datasets

Read-onlyIdempotent

List all preset datasets from OECD data sources. Filter results by keyword to quickly find relevant datasets for economic analysis.

Instructions

列出 OECD 数据源支持的所有预置数据集。

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": "ext_oecd_datasets"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	No	按关键词过滤

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Apr 25, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds no additional behavioral context (e.g., pagination, rate limits). With annotations present, a 3 is appropriate.

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?

Single sentence in Chinese, no wasted words. Front-loaded with purpose. Appropriate for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but without an output schema, the description could hint at return format (e.g., dataset names, IDs). It does not, leaving some ambiguity. Still, it is mostly complete for listing datasets.

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%; the description adds no extra meaning beyond the schema. Baseline 3 is adequate as the parameter is optional and has its own description.

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 tool lists all pre-built datasets from the OECD data source. The verb 'list' and resource 'datasets' are specific, and the name distinguishes it from sibling tools like 'ext_oecd'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., 'ext_oecd' for actual data). It does not mention when not to use it or provide context on filtering.

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