Skip to main content
Glama
Sign In
OECD MCP Server

OECD MCP Server

by isakskogstad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_categories

Retrieve the full list of OECD data categories (17 topics) to navigate datasets on economy, health, education, environment, and more.

Instructions

Get all available OECD data categories (17 categories covering all topics: Economy, Health, Education, Environment, etc.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A3.8/5.0
Behavior3/5

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

The description discloses the scope and content of the output (17 categories covering all topics) but does not mention any behavioral nuances like caching, pagination, or authorization requirements. Without annotations, the description carries the full burden; it is adequate but not thorough.

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?

The description is a single sentence with no wasted words. It efficiently communicates the tool's function, scope, and examples.

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 no-parameter tool with no output schema, the description provides the essential information: what it returns (all categories) and a preview of the data (17 examples). However, it could be enhanced by noting the output format or if any filtering is supported.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since there are no parameters and the schema coverage is 100% (empty schema), the description adds relevant context about what the tool returns, which goes beyond the schema. According to guidelines, baseline for 0 params is 4.

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 it retrieves all available OECD data categories, specifies the exact number (17), and provides a representative list of topics. This distinguishes it from siblings like list_categories_detailed, which likely returns more detailed information.

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 is provided on when to use this tool versus alternatives such as list_categories_detailed or search tools. The agent must infer usage based on the name and brief description.

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