Skip to main content
Glama
Sign In
OECD MCP Server

OECD MCP Server

by isakskogstad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_dataflows

Search OECD datasets by keyword to find matching dataflows with identifiers, names, and descriptions.

Instructions

Search for OECD datasets (dataflows) by keyword. Returns matching datasets with their IDs, names, and descriptions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_dataflows"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query to find relevant datasets
limitNoMaximum number of results to return (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. States it returns matching datasets with fields, but does not disclose auth needs, rate limits, pagination, or error behavior. Adequate for a simple search, but lacks depth.

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, clear sentence with no wasted words. Front-loaded with purpose.

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 search tool with 2 parameters and no output schema, the description covers the essentials: what it searches, how (keyword), and what is returned. Could mention pagination or sorting, but not critical.

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% for both parameters (query, limit). Description adds little beyond schema, as the schema already explains each parameter. 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?

Clearly states 'Search for OECD datasets (dataflows) by keyword', specifying the verb (search), resource (datasets), and output (IDs, names, descriptions). Distinguishes from sibling 'list_dataflows' which would list all, while this searches by keyword.

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?

Implies usage when keyword-based search is needed, and sibling 'list_dataflows' suggests alternative for browsing all. However, no explicit when-not-to-use or prerequisites mentioned.

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