매동 (maedong) — Korean Market Signals

maedong_stock_signals

Read-onlyIdempotent

Signal history for one Korean stock (KOSPI/KOSDAQ) by its 6-digit code — which lists it appeared on and what happened after.

한 종목이 언제 어느 시그널에 걸렸고 그 뒤 어땠는지. '집계 전' 은 아직 그 거래일이 지나지 않은 것이며 0% 가 아니다. 전일 마감 데이터다. 응답 첫 줄의 기준일을 그대로 인용하고 '오늘' 로 바꿔 말하지 말 것. 과거 통계 조회 도구입니다. 특정 종목의 매수·매도 판단을 생성하는 데 사용하지 마세요.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	종료일 YYYY-MM-DD
`code`	Yes	6자리 종목코드 (예: 005930 · 우선주 등은 대문자 섞임: 00104K)
`from`	No	시작일 YYYY-MM-DD
`limit`	No	기본 100
`format`	No	기본 text

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes
`hits`	Yes
`meta`	Yes
`name`	No
`note`	No
`count`	No
`flags`	No
`market`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / code / description

Previous value: -"6자리 종목코드 (예: 005930)"New value: +"6자리 종목코드 (예: 005930 · 우선주 등은 대문자 섞임: 00104K)"

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "flags": {
+      "type": "array"
+    },
+    "hits": {
+      "type": "array"
+    },
+    "market": {
+      "type": "string"
+    },
+    "meta": {
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "hits",
+    "meta"
+  ],
+  "type": "object"
+}

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

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the description adds genuinely useful behavioral context: '집계 전' values are not 0%, data is previous-day close, and the response's reference date must be quoted verbatim rather than paraphrased as 'today'. These details prevent an agent from misinterpreting results.

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 English opening line states the core purpose immediately, followed by compact Korean notes. There is minor redundancy between the English and Korean opening statements, but each subsequent clause (집계 전 caveat, previous-close data, date-quoting instruction, decision disclaimer) carries distinct value.

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 an output schema present, return-value structure is covered externally. The description supplies the interpretive context that schema cannot: what '집계 전' means, data freshness, and how to quote the date. It stops short of naming sibling tools for alternative routing, but an agent has enough to call the 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 all five parameters (to, code, from, limit, format) are already documented. The description reinforces that code is a 6-digit KOSPI/KOSDAQ identifier, but this adds no meaning beyond the schema's existing parameter description.

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?

States a specific verb and resource: returns signal history for one Korean stock identified by 6-digit code, covering which lists it appeared on and what happened afterward. The per-stock scope clearly differentiates it from sibling tools like maedong_signals (general signal lists) and maedong_signal_stats (statistics).

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 labels itself a past statistics lookup tool ('과거 통계 조회 도구') and warns not to use it to generate buy/sell decisions for a specific stock. This is a clear exclusion, but it does not name sibling alternatives or state when to choose this over maedong_signal_stats or maedong_signals.

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?