Skip to main content
Glama

Ecos Kr

by io.github.pipeworx-io

Ecos Series Items

ecos_series_items
Read-onlyIdempotent

List the items (sub-series) within a Bank of Korea ECOS statistic table. Most stat_codes have multiple sub-items (e.g., the exchange-rate table has rows per currency: USD, JPY, EUR, ...). Pass the stat_code from ecos_search_tables; returns item_code, item_name, cycle, data_count, start/end period. Use to discover the exact item codes needed by ecos_get_series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items to return (default 30, max 100).
stat_codeYesStatistic table code from ecos_search_tables (e.g., "731Y001" for exchange rates).

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint false. Description adds behavioral context: mentions most stat_codes have multiple sub-items, gives example (exchange rates with currencies), and lists returned fields (item_code, item_name, cycle, data_count, start/end period). No contradictions 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 that front-load the main action and purpose. No unnecessary words; every sentence provides essential information (what, why, how). Highly efficient.

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?

Given the tool's simplicity, good annotations, and clear description of input, output, and relationship to siblings, it is largely complete. Lacks details on error handling or pagination, but these are not critical for a listing tool with openWorldHint.

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% with both parameters described. Description adds value by mentioning stat_code comes from ecos_search_tables and provides an example value ('731Y001'). However, it does not add meaning beyond the schema for the limit parameter (default/max already in schema). Baseline 3 with minor extra value.

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 it lists sub-items within a Bank of Korea ECOS statistic table, using specific verb 'List' and resource 'items (sub-series) within a Bank of Korea ECOS statistic table'. Distinguishes from siblings like ecos_get_series and ecos_search_tables by explaining its role in discovering item codes needed later.

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?

Explicitly instructs to pass stat_code from ecos_search_tables and notes the purpose is to discover item codes for ecos_get_series. Provides clear context on when to use (to get sub-items) and relationship to other tools, though it doesn't explicitly state when not to use.

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

All Ecos Kr 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

A3.8/5.0
Disambiguation3/5

Several tool families overlap heavily: ask_pipeworx and ask_pipeworx_beta are functionally identical today, and the polymarket_edges/arbitrage/fill_risk/kalshi_spread family plus entity_profile/recent_changes/compare_entities cover adjacent jobs. The descriptions are detailed enough to separate them with careful reading, but an agent could easily select the wrong one without deep inspection.

Naming Consistency3/5

The set has recognizable prefixes like ecos_, ask_pipeworx, and polymarket_, but it also mixes verb_noun names (validate_claim, discover_tools), bare verbs (remember, forget, recall), reversed/gerund forms (bet_research, pipeworx_trending), and special tokens (generate_llms_txt). The naming is readable on a per-family basis but not predictable across the full surface.

Tool Count2/5

35 tools is above the comfortable range for a coherent tool set, and several entries are near-duplicates or wrappers: ask_pipeworx_beta is currently identical to ask_pipeworx, and scan_competitor_ai_presence wraps ai_visibility_check. The prediction-market and company-research families could be consolidated without losing capability.

Completeness4/5

For the server's broad scope, lifecycle coverage is strong: ECOS has search/items/get/indicators, subscriptions have create/list/read/cancel, memory has save/read/delete, and the data-research surface covers lookup, grounded verification, comparison, profiles, changes, and discovery. Minor gaps exist, such as no direct tool to fetch a pipeworx:// record by URI or execute a single catalog tool directly, but these are workable.

Resources