Skip to main content
Glama

oecd-mcp-server

by io.github.cyanheads

Oecd Search Datasets

oecd_search_datasets
Read-onlyIdempotent

Search OECD dataflows by keyword or theme, matching against dataflow names and descriptions. Returns flow_ref identifiers, names, and agency IDs for use with oecd_get_dataset_info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1–100, default 20).
queryYesKeyword or phrase to search for in dataflow names and descriptions — e.g. "GDP", "employment", "education". Every whitespace-separated token must appear somewhere in the name or description.
offsetNoZero-based index of the first match to return, applied before limit. Page through results past the limit by advancing it; an offset at or past total_matches returns an empty list.
agency_idNoOptional agency identifier to restrict the search scope — e.g. "OECD.SDD.NAD". Obtain valid agency IDs from oecd_list_agencies.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
offsetNoZero-based index of the first returned result within the full match list.
sourceNoData source attribution — always "OECD".
dataflowsNoMatching dataflows for the requested page, up to the requested limit.
totalCountNoTotal dataflows matching the query, disclosed when matches remain beyond the returned page.
result_countNoNumber of results returned (may be less than total_matches).
total_matchesNoTotal dataflows matching the query before applying offset and limit.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld behavior, so the description only needs to add context. It adds the matching behavior (against names and descriptions) and the specific return payload, which is useful beyond the annotations. No contradiction with the annotation hints.

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 filler; the search action and matching scope are front-loaded, and the return-value note is relevant to downstream tool selection.

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?

For a read-only search tool with a fully documented schema, rich annotations, and an output schema, the description covers the necessary selection and invocation context. It tells the agent what to expect and how the result connects to oecd_get_dataset_info.

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%, and the input schema already documents query, limit, offset, and agency_id with examples and constraints. The tool description adds no parameter-level meaning, so the baseline 3 applies.

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 specifies a concrete action (search OECD dataflows by keyword or theme), the matching target (dataflow names and descriptions), and the returned identifiers (flow_ref, names, agency IDs). It also positions the tool as the discovery step preceding oecd_get_dataset_info, distinguishing it from sibling query/dataframe tools.

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 description makes the intended workflow clear: search by keyword or theme to obtain identifiers 'for use with oecd_get_dataset_info.' It does not explicitly list when not to use it or name alternatives, so it stops short of full exclusion guidance.

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

All oecd-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool occupies a distinct stage of the OECD data workflow: search/agency discovery, dataset structure, dimension values, observation querying, and SQL analysis of spilled results. The two query tools are differentiated by source (SDMX vs staged DataCanvas tables), and the two metadata tools are differentiated by purpose (key structure vs codelist values).

Naming Consistency4/5

Most tools follow an oecd_<verb>_<noun> pattern (get, list, query, search), and all share the oecd_ prefix and snake_case. The two dataframe tools shift to oecd_dataframe_<verb>, a minor but noticeable ordering deviation.

Tool Count5/5

Seven tools is well-scoped for an OECD data access server: discovery, metadata, dimension values, observation query, and large-result SQL handling. There is no apparent bloat or overly thin coverage.

Completeness5/5

The set covers the full journey from finding datasets and agencies, learning the SDMX key structure, resolving dimension codes, fetching observations, and analyzing spilled datasets with SQL. This is a complete read-only workflow for the domain.

Resources