Skip to main content
Glama
Sign In

korea-realty

by app.sallim
OverviewDiscussionsAdmin

거시 지표 (기준금리·KOSPI·M2 시계열)

realty_macro_indicators
Read-onlyIdempotent

한국 기준금리·KOSPI·M2, 미 연준금리·S&P500 등 거시 지표의 월별 시계열을 조회한다. "금리가 집값에 어떤 영향?"류 배경 분석용.

⚠️ 계열마다 신선도가 다르다 — 원천·공표 주기가 달라 최신 달이 계열마다 갈린다(예: M2는
공표가 한두 달 늦다). 계열별 실제 최신 시점은 응답 meta.series_as_of가 정본이다 — 이 설명에
날짜를 적지 않는다(적힌 날짜는 낡는다). 밀린 계열을 "지금 금리"로 인용하지 말고 반드시
그 계열의 시점을 함께 밝혀라.

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

Input Schema

NameRequiredDescriptionDefault
monthsNo최근 몇 개월치 (허용 범위 1~240)
indicatorsNo쉼표 구분 지표명: bok_base_rate(한국 기준금리 %), kospi(월말 종가), korea_m2(M2 평잔·원계열, 조원), fed_rate(미 연준금리 월평균 %), us_m2(미 M2 계절조정 $B), sp500, btc_usd, eth_usd(월말 종가). 비우면 전체. 목록에 없는 이름은 거절한다(조용히 버리지 않는다)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "realty_macro_indicatorsDictOutput",
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changed
    • changedInput schema / properties / indicators / description
      Previous value: -"쉼표 구분 지표명: bok_base_rate(한국 기준금리 %), kospi(월말 종가), korea_m2(M2 평잔·원계열, 조원), fed_rate(미 연준금리 월평균 %), sp500, btc_usd, eth_usd(월말 종가). 비우면 전체"New value: +"쉼표 구분 지표명: bok_base_rate(한국 기준금리 %), kospi(월말 종가), korea_m2(M2 평잔·원계열, 조원), fed_rate(미 연준금리 월평균 %), us_m2(미 M2 계절조정 $B), sp500, btc_usd, eth_usd(월말 종가). 비우면 전체. 목록에 없는 이름은 거절한다(조용히 버리지 않는다)"
  3. Changed1 schema field changed
    • changedInput schema / properties / months / description
      Previous value: -"최근 몇 개월치"New value: +"최근 몇 개월치 (허용 범위 1~240)"
  4. Changed1 schema field changed
    • changedInput schema / properties / indicators / description
      Previous value: -"쉼표 구분 지표명: bok_base_rate(한국 기준금리 %), kospi, korea_m2(조원), fed_rate(미 연준금리 %), sp500, btc_usd, eth_usd. 비우면 전체"New value: +"쉼표 구분 지표명: bok_base_rate(한국 기준금리 %), kospi(월말 종가), korea_m2(M2 평잔·원계열, 조원), fed_rate(미 연준금리 월평균 %), sp500, btc_usd, eth_usd(월말 종가). 비우면 전체"
  5. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial non-obvious behavior beyond the readOnly/idempotent annotations: publication cadence differs per series, the latest month varies by series (M2 lags one to two months), and meta.series_as_of in the response is the authority rather than any date in the description. This is exactly the kind of operational caveat annotations cannot convey.

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?

Purpose is front-loaded in the first sentence, then the freshness warning, which earns its length given the real risk of misquoting a lagged series. Slightly verbose in restating the no-hardcoded-dates rationale, but nothing is wasted.

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?

With no output schema, the description usefully points at meta.series_as_of but does not otherwise describe the returned shape (e.g., date/value structure). For a two-param, read-only, default-everything tool with full schema coverage, this is nearly complete.

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% — the schema already enumerates every indicator key, units, the 1~240 month range, and the reject-unknown-names behavior. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — retrieving monthly time series for named macro indicators (한국 기준금리·KOSPI·M2, 미 연준금리·S&P500). It is distinguishable from trend/market siblings by being macro-level and cross-country, though it never names a sibling tool explicitly.

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?

Gives a clear use context ('금리가 집값에 어떤 영향?'류 배경 분석용) and concrete do/don't guidance about freshness — don't quote a lagged series as the current rate, always state the series' as-of point. No explicit alternative-tool routing, so it stops short of a 5.

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

All korea-realty toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources