Skip to main content
Glama

매동 (maedong) — Korean Market Signals

maedong_signals

Read-onlyIdempotent

Korean stock market (KOSPI/KOSDAQ) screener lists — which stocks are on a given trading day's signal lists (price, chart, value, and lists built on foreign/institutional net buying and short-selling activity), or the catalog of all lists.

기준일에 어떤 종목이 어느 시그널에 올랐는지 조회한다. signal 을 생략하면 그날 목록별 종목 수만 주므로 어느 목록을 볼지 먼저 고를 때 쓴다. 정리매매·거래정지 종목은 경고와 함께 표시된다. 전일 마감 데이터다. 응답 첫 줄의 기준일을 그대로 인용하고 '오늘' 로 바꿔 말하지 말 것. 과거 통계 조회 도구입니다. 특정 종목의 매수·매도 판단을 생성하는 데 사용하지 마세요.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo기준일 YYYY-MM-DD. 생략하면 최신 거래일
limitNo기본 50
cursorNo이전 응답이 준 cursor 값
formatNo기본 text
signalNo목록 slug. 생략하면 목록별 건수 색인

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
metaYes
noteNo
ruleNo
countNo
itemsNo
labelNo
totalNo
signalNo
signalsNo
excludedNo
next_cursorNo
metric_labelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / signal / enum
      Previous value: -[
      -  "accumulation",
      -  "both-buy",
      -  "box-breakout",
      -  "disparity-cold",
      -  "disparity-hot",
      -  "distribution",
      -  "drawdown-52w",
      -  "dry-surge",
      -  "foreign-buy-streak",
      -  "gainers",
      -  "gap-up",
      -  "golden-cross",
      -  "golden-cross-flow",
      -  "high-52w",
      -  "high-dividend",
      -  "large-gainers",
      -  "losers",
      -  "low-52w",
      -  "low-per",
      -  "low52-surge",
      -  "ma-stack",
      -  "ma-stack-flow",
      -  "market-cap",
      -  "momentum-12-1",
      -  "retail-only",
      -  "rsi-oversold",
      -  "short-surge",
      -  "short-top",
      -  "streak-up",
      -  "surge-pullback",
      -  "turnover",
      -  "turnover-gapdown",
      -  "value-surge",
      -  "value-top"
      -]New value: +[
      +  "accumulation",
      +  "both-buy",
      +  "box-breakout",
      +  "disparity-cold",
      +  "disparity-hot",
      +  "distribution",
      +  "drawdown-52w",
      +  "dry-surge",
      +  "foreign-buy-streak",
      +  "gainers",
      +  "gap-up",
      +  "golden-cross",
      +  "golden-cross-flow",
      +  "high-52w",
      +  "high-dividend",
      +  "large-gainers",
      +  "losers",
      +  "low-52w",
      +  "low-per",
      +  "low52-surge",
      +  "ma-stack",
      +  "ma-stack-flow",
      +  "market-cap",
      +  "momentum-12-1",
      +  "momentum-weighted",
      +  "retail-only",
      +  "rsi-oversold",
      +  "short-surge",
      +  "short-top",
      +  "streak-up",
      +  "surge-pullback",
      +  "trend-breakout",
      +  "turnover",
      +  "turnover-gapdown",
      +  "value-surge",
      +  "value-top"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / signal / enum
      Previous value: -[
      -  "accumulation",
      -  "both-buy",
      -  "box-breakout",
      -  "disparity-cold",
      -  "disparity-hot",
      -  "distribution",
      -  "drawdown-52w",
      -  "dry-surge",
      -  "foreign-buy-streak",
      -  "gainers",
      -  "gap-up",
      -  "golden-cross",
      -  "golden-cross-flow",
      -  "high-52w",
      -  "high-dividend",
      -  "large-gainers",
      -  "losers",
      -  "low-52w",
      -  "low-per",
      -  "low52-surge",
      -  "ma-stack",
      -  "ma-stack-flow",
      -  "market-cap",
      -  "momentum-12-1",
      -  "program-buy",
      -  "retail-only",
      -  "rsi-oversold",
      -  "short-surge",
      -  "short-top",
      -  "streak-up",
      -  "surge-pullback",
      -  "turnover",
      -  "turnover-gapdown",
      -  "value-surge",
      -  "value-top"
      -]New value: +[
      +  "accumulation",
      +  "both-buy",
      +  "box-breakout",
      +  "disparity-cold",
      +  "disparity-hot",
      +  "distribution",
      +  "drawdown-52w",
      +  "dry-surge",
      +  "foreign-buy-streak",
      +  "gainers",
      +  "gap-up",
      +  "golden-cross",
      +  "golden-cross-flow",
      +  "high-52w",
      +  "high-dividend",
      +  "large-gainers",
      +  "losers",
      +  "low-52w",
      +  "low-per",
      +  "low52-surge",
      +  "ma-stack",
      +  "ma-stack-flow",
      +  "market-cap",
      +  "momentum-12-1",
      +  "retail-only",
      +  "rsi-oversold",
      +  "short-surge",
      +  "short-top",
      +  "streak-up",
      +  "surge-pullback",
      +  "turnover",
      +  "turnover-gapdown",
      +  "value-surge",
      +  "value-top"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / signal / enum
      Previous value: -[
      -  "accumulation",
      -  "both-buy",
      -  "box-breakout",
      -  "disparity-cold",
      -  "disparity-hot",
      -  "distribution",
      -  "drawdown-52w",
      -  "dry-surge",
      -  "foreign-buy-streak",
      -  "gainers",
      -  "gap-up",
      -  "golden-cross",
      -  "high-52w",
      -  "high-dividend",
      -  "large-gainers",
      -  "losers",
      -  "low-52w",
      -  "low-per",
      -  "low52-surge",
      -  "ma-stack",
      -  "market-cap",
      -  "momentum-12-1",
      -  "program-buy",
      -  "retail-only",
      -  "rsi-oversold",
      -  "short-surge",
      -  "short-top",
      -  "streak-up",
      -  "surge-pullback",
      -  "turnover",
      -  "turnover-gapdown",
      -  "value-surge",
      -  "value-top"
      -]New value: +[
      +  "accumulation",
      +  "both-buy",
      +  "box-breakout",
      +  "disparity-cold",
      +  "disparity-hot",
      +  "distribution",
      +  "drawdown-52w",
      +  "dry-surge",
      +  "foreign-buy-streak",
      +  "gainers",
      +  "gap-up",
      +  "golden-cross",
      +  "golden-cross-flow",
      +  "high-52w",
      +  "high-dividend",
      +  "large-gainers",
      +  "losers",
      +  "low-52w",
      +  "low-per",
      +  "low52-surge",
      +  "ma-stack",
      +  "ma-stack-flow",
      +  "market-cap",
      +  "momentum-12-1",
      +  "program-buy",
      +  "retail-only",
      +  "rsi-oversold",
      +  "short-surge",
      +  "short-top",
      +  "streak-up",
      +  "surge-pullback",
      +  "turnover",
      +  "turnover-gapdown",
      +  "value-surge",
      +  "value-top"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / signal / enum
      Previous value: -[
      -  "accumulation",
      -  "both-buy",
      -  "disparity-cold",
      -  "disparity-hot",
      -  "distribution",
      -  "drawdown-52w",
      -  "dry-surge",
      -  "foreign-buy-streak",
      -  "gainers",
      -  "gap-up",
      -  "high-52w",
      -  "high-dividend",
      -  "large-gainers",
      -  "losers",
      -  "low-52w",
      -  "low-per",
      -  "low52-surge",
      -  "market-cap",
      -  "momentum-12-1",
      -  "program-buy",
      -  "retail-only",
      -  "short-surge",
      -  "short-top",
      -  "streak-up",
      -  "surge-pullback",
      -  "turnover",
      -  "turnover-gapdown",
      -  "value-surge",
      -  "value-top"
      -]New value: +[
      +  "accumulation",
      +  "both-buy",
      +  "box-breakout",
      +  "disparity-cold",
      +  "disparity-hot",
      +  "distribution",
      +  "drawdown-52w",
      +  "dry-surge",
      +  "foreign-buy-streak",
      +  "gainers",
      +  "gap-up",
      +  "golden-cross",
      +  "high-52w",
      +  "high-dividend",
      +  "large-gainers",
      +  "losers",
      +  "low-52w",
      +  "low-per",
      +  "low52-surge",
      +  "ma-stack",
      +  "market-cap",
      +  "momentum-12-1",
      +  "program-buy",
      +  "retail-only",
      +  "rsi-oversold",
      +  "short-surge",
      +  "short-top",
      +  "streak-up",
      +  "surge-pullback",
      +  "turnover",
      +  "turnover-gapdown",
      +  "value-surge",
      +  "value-top"
      +]
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "count": {
      +      "type": "integer"
      +    },
      +    "date": {
      +      "type": "string"
      +    },
      +    "excluded": {
      +      "type": "array"
      +    },
      +    "items": {
      +      "type": "array"
      +    },
      +    "label": {
      +      "type": "string"
      +    },
      +    "meta": {
      +      "type": "object"
      +    },
      +    "metric_label": {
      +      "type": "string"
      +    },
      +    "next_cursor": {
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "rule": {
      +      "type": "string"
      +    },
      +    "signal": {
      +      "type": "string"
      +    },
      +    "signals": {
      +      "type": "array"
      +    },
      +    "total": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "date",
      +    "meta"
      +  ],
      +  "type": "object"
      +}
  6. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that liquidation or suspended stocks are shown with a warning, that data is prior-day closing data, that the base date in the first response line must be quoted and not paraphrased as 'today', and that the tool is historical statistics only. These are non-obvious behavioral constraints an agent would otherwise get wrong.

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 purpose is front-loaded and most sentences carry distinct, actionable content (counts-index fallback, warning flags, data freshness, date-quoting rule, scope restriction). It is somewhat long and alternates between English and Korean, but there is no dead weight.

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 explanation is unnecessary, and the description covers date semantics, list-catalog fallback, data staleness, warning indicators, and scope limits. The main gap is that it doesn't help disambiguate from its siblings, which leaves a residual selection risk.

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 `date`, `limit`, `cursor`, `format`, and `signal` are already documented; the baseline is 3. The description reinforces the meaning of an omitted `signal` (counts-only index), but adds little syntax or format detail beyond what the schema already states.

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?

The description names a specific verb and resource: it retrieves which stocks appear on a given trading day's KOSPI/KOSDAQ signal lists, or the catalog of lists when no signal is given. This is concrete and scannable, but it never names or contrasts with the close siblings (maedong_stock_signals, maedong_signal_stats), so an agent must infer the boundary itself.

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?

It gives clear usage context: omitting `signal` returns only per-list counts, so call it first when deciding which list to view, and it explicitly says not to use it to generate buy/sell judgments. It lacks explicit routing to the named sibling tools for per-stock or statistical queries.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources