Skip to main content
Glama

oecd-mcp-server

by io.github.cyanheads

Oecd Get Dimension Values

oecd_get_dimension_values
Read-onlyIdempotent

Fetch the valid codes and labels for one dimension of a dataflow. Use to resolve human-readable names (countries, measures) to SDMX codes before querying with oecd_query_dataset. Pass query to match a code or label by substring — codelists run to a thousand-plus entries, and the response is a page of at most limit codes either way.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum codes to return (1–500, default 50).
queryNoCase-insensitive substring matched against both the code and its label, so "PA" and "percent" each reach the code "PA" / "Percent per annum". Omit to page the whole codelist.
offsetNoZero-based index of the first code to return within the matching list, applied before limit. Advance it to page; an offset past the last match returns an empty page.
flow_refYesFull flow reference — e.g. "OECD.SDD.NAD,DSD_NAAG@DF_NAAG_I", or the bare "OECD.TAD.ARP,DF_AEI2024_DASHBOARD" form for a dataflow published without a datastructure prefix. Obtain from oecd_search_datasets.
dimension_idYesDimension identifier to fetch codes for — e.g. "REF_AREA" or "MEASURE". Obtain valid dimension IDs from oecd_get_dataset_info.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codesNoThe requested page of codes, after query, offset, and limit are applied.
errorNoPresent when the call failed. Absent on success.
noticeNoPresent when the page needs explaining — the dimension has no codelist, the query matched nothing, or codes remain beyond the page. States how to reach the rest.
sourceNoData source attribution — always "OECD".
flow_refNoThe flow reference this dimension belongs to.
code_countNoNumber of codes in this page — not the size of the dimension's codelist.
totalCountNoCodes matching before offset and limit, disclosed when the page does not cover them all.
dimension_idNoThe dimension whose codes are listed.
effectiveQueryNoThe substring filter as applied. Absent when the whole codelist was paged.

TDQS

A4.2/5.0
Behavior4/5

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

The description adds behavioral context beyond the readOnly/openWorld/idempotent annotations: responses are paginated at 'at most limit codes either way,' and codelists 'run to a thousand-plus entries,' explaining why querying and paging matter. No contradiction with 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 sentences deliver purpose, usage context, a rationale for the query parameter, and pagination behavior. Everything earns its place and the key action is front-loaded.

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?

Input schema fully documents parameters, an output schema exists, and the description supplies the workflow context and pagination behavior. It is complete for practical use, though explicit alternative tool guidance would make it stronger.

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%, so the baseline applies. The description adds workflow context but does not materially elaborate on individual parameter meanings beyond what the schema already documents, so it neither compensates nor needs to.

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 states a specific verb and resource: 'Fetch the valid codes and labels for one dimension of a dataflow.' It also frames the tool's role in the workflow, resolving human-readable names to SDMX codes before using oecd_query_dataset, which differentiates it from sibling 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?

Clear context is provided: use this tool to resolve names to codes before querying with oecd_query_dataset. It does not enumerate exclusions or alternative tools explicitly, but the intended position in the workflow is unambiguous.

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