매동 (maedong) — Korean Market Signals

maedong_market

Read-onlyIdempotent

Korean market snapshot — KOSPI/KOSDAQ index levels, market breadth, valuation percentiles, and macro series (FX, bond yields, base rate).

기준일의 지수·시장 폭·밸류에이션·매크로. 백분위는 2020-04 이후 분포에서의 위치이고, 재무 커버리지는 재무가 있는 종목의 시총 비중이다. 매크로에서 '마지막 변경분' 이라고 적힌 값(기준금리)은 그날 움직인 것이 아니다. 전일 마감 데이터다. 응답 첫 줄의 기준일을 그대로 인용하고 '오늘' 로 바꿔 말하지 말 것. 과거 통계 조회 도구입니다. 특정 종목의 매수·매도 판단을 생성하는 데 사용하지 마세요.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	기준일 YYYY-MM-DD. 생략하면 최신 거래일
`format`	No	기본 text

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes
`meta`	Yes
`macro`	No
`breadth`	No
`indices`	Yes
`valuation`	No
`value_vs_20d_avg`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "breadth": {
+      "type": "object"
+    },
+    "date": {
+      "type": "string"
+    },
+    "indices": {
+      "type": "array"
+    },
+    "macro": {
+      "type": "array"
+    },
+    "meta": {
+      "type": "object"
+    },
+    "valuation": {
+      "type": "array"
+    },
+    "value_vs_20d_avg": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "date",
+    "indices",
+    "meta"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 13, 2026
- addedInput schema / properties / format / description
```
Added value: +"기본 text"
```
First observedSep 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is clear. The description adds significant behavioral context: it explains that the data is from the previous close (not intraday), that percentiles are relative to the distribution since 2020-04, and that the 'last change' value for the base rate does not reflect a daily movement. These are non-obvious nuances an agent must know to interpret results correctly.

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 compact yet information-dense. It front-loads the core purpose, then adds necessary caveats in a logical order: percentiles definition, financial coverage, the non-daily nature of macro changes, the instruction about quoting the baseline date, and the explicit exclusion of investment advice. Every sentence earns its place without redundancy.

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?

Given the output schema exists and annotations cover the read-only and idempotent nature, the description fills all remaining gaps. It defines key metrics (percentiles, financial coverage), clarifies temporal semantics (previous close, not daily change), and gives usage constraints. An agent has everything needed to call and interpret this tool correctly.

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%, so both parameters (date and format) are fully documented in the schema. The description does not add syntax or format details beyond that, but it does provide context about how to interpret the date (as a baseline date) and warns against rephrasing it. This is slightly beyond schema but not substantial, so a baseline 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 clearly states the tool provides a Korean market snapshot with specific components: index levels, market breadth, valuation percentiles, and macro series. It names the exact data types and sets expectations about what is included, making its purpose unambiguous and distinct from sibling tools that focus on regimes, signals, or stats.

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 explicitly frames the tool as a historical statistics query tool and warns against using it to generate buy/sell judgments for specific stocks. It also provides a precise usage instruction: do not paraphrase the baseline date as 'today'. While it does not name alternative tools, it gives clear context on when to use this tool (historical stats) and what not to use it for (investment advice).

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

All 매동 (maedong) — Korean Market Signals tools Inspect

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

Need Help?