Skip to main content
Glama

Ecos Kr

by io.github.pipeworx-io

Ecos Key Indicators

ecos_key_indicators
Read-onlyIdempotent

Bank of Korea headline economic indicators: M1/M2 money supply, KRW/USD + KRW/JPY exchange rates, base interest rate, CPI, PPI, GDP growth, current account balance, household debt, unemployment, housing index — 101 series total in one call. Each row: indicator name, current value, cycle date, unit. Use for "what is Korea's [exchange rate / interest rate / CPI / GDP] right now". Updates daily.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax indicators to return (default 50, max 100).

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety and idempotency. The description adds update frequency and row structure, providing useful behavioral context without contradiction.

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 highly concise, conveying the scope and usage in just a few sentences. Every sentence adds value, and the structure is clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only aggregation tool with one parameter, the description sufficiently covers the content, return format, update schedule, and usage. No gaps given the context.

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?

The single parameter 'limit' is fully described in the schema (100% coverage). The description does not add further parameter semantics, so a 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?

The description explicitly lists the types of indicators and states it is a single-call aggregation of 101 series, clearly distinguishing from sibling tools like ecos_get_series which likely handle individual series. It also provides example queries.

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?

Provides explicit usage examples for common queries, but does not mention when to avoid this tool or use sibling tools like ecos_get_series for more granular data.

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