Skip to main content
Glama
kgy0617

Global Economic Statistical MCP

by kgy0617
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search statistics

search_statistics
Read-onlyIdempotent

Locate economic statistics from OECD, IMF, BIS, and Bank of Korea. Search concepts, dataflows, tables, items, and key statistics to find the right series before retrieval.

Instructions

Search concepts, OECD/IMF/BIS dataflows and Bank of Korea (ECOS) tables and items. The first step before retrieval.

scope:
- "all" (default): concepts + ECOS items + ECOS tables + international dataflows
- "concepts": country-agnostic concepts mapped across institutions (retrieve with get_data(indicator=..., country=...))
- "items": ECOS items (e.g. '쌀' rice, '휘발유' gasoline) from an index generated from the ECOS API
- "tables": ECOS tables (without query: children of the parent_code category)
- "dataflows": OECD, IMF and BIS dataflows (every word must match the English name or id; source narrows the institution)
- "key_statistics": latest values of the Bank of Korea's 100 key statistics

Args:
    query: search terms (e.g. "policy rate", "unemployment", "inflation", "물가")
    scope: "all" | "concepts" | "items" | "tables" | "dataflows" | "key_statistics"
    source: institution for dataflow search (OECD | IMF | BIS)
    parent_code: ECOS table category code
    searchable_only: ECOS tables that can be queried only
    limit: maximum results per category
    language: language of key_statistics ("kr" | "en")

Returns:
    results per category (concepts, items, tables, dataflows, key_statistics)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNo
scopeNoall
sourceNo
languageNokr
parent_codeNo
searchable_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and idempotentHint, so the description doesn't need to repeat safety. It adds valuable behavioral detail such as how dataflows require every word to match the English name/id, tables without query return children of parent_code, and key_statistics returns latest values. This goes beyond annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a one-line summary, a scope section, an Args list, and a Returns note. It is a bit long but every bullet adds necessary detail. It is front-loaded with the purpose and avoids redundancy.

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 search tool with no output schema, the description covers the main aspects: what each scope searches, how parameters affect results, and that results are returned per category. It lacks detail on the exact fields of each result item, but this is a minor gap given the tool's exploratory role.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by explaining all seven parameters with examples and context: query gives example terms, scope enumerates all valid values and meanings, source specifies institutions, parent_code, searchable_only, limit, and language. This is far more than the bare schema provides.

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 searches concepts, OECD/IMF/BIS dataflows, and ECOS tables/items, and explicitly labels itself as 'The first step before retrieval,' which distinguishes it from sibling retrieval tools like get_data. The verb and resource are specific, and the scope section adds granularity.

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 says it is the first step before retrieval, implying use before get_data, and for concepts it even specifies how to retrieve with get_data. However, it does not explicitly list when not to use it or name all alternative tools, though the scope definitions provide clear context for choosing scopes.

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