dart-risk-mcp

list_disclosures_by_stock

Retrieve recent DART disclosure receipt numbers by stock code for document lookup and risk analysis. Filter by date range or lookback period.

Instructions

종목코드로 최근 공시의 접수번호(rcept_no) 목록을 조회한다.

반환된 접수번호는 get_disclosure_document, view_disclosure, check_disclosure_risk 등에 바로 사용할 수 있다.

Args: stock_code: 종목코드 6자리 (예: "086520") lookback_years: 조회 기간(년). 기본 1년, 1~5년 범위.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to_date`	No
`from_date`	No
`stock_code`	Yes
`lookback_days`	No
`lookback_years`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.21.25Sep 1, 2026

addedInput schema / properties / from_date

Added value: +{
+  "default": "",
+  "title": "From Date",
+  "type": "string"
+}

addedInput schema / properties / to_date

Added value: +{
+  "default": "",
+  "title": "To Date",
+  "type": "string"
+}

Changed4 schema fields changedv1.4.0Jun 21, 2026
- addedInput schema / properties / lookback_days / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / lookback_days / default
```
Previous value: -90New value: +null
```
- removedInput schema / properties / lookback_days / type
```
Removed value: -"integer"
```
- addedInput schema / properties / lookback_years
```
Added value: +{
+  "default": 1,
+  "title": "Lookback Years",
+  "type": "integer"
+}
```
First observedv1.0.3May 31, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the main behavioral outcome (returns a list of rcept_no) and notes downstream compatability. However, it does not mention sorting, result limits, exact date-boundary behavior, or potential side effects—though '조회한다' implies a read operation. No contradiction with annotations.

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 and front-loaded, with the core purpose stated first and an Args section that is easy to scan. Every sentence adds value, and there is no redundant explanation of the schema.

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

Completeness2/5

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

With 5 parameters, no annotations, and 0% schema description coverage, the description is incomplete because it documents only two of them. The presence of an output schema mitigates the return-value gap, but the undocumented date-related parameters leave a material hole in the tool contract.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does well for stock_code (6-digit example) and lookback_years (default 1 year, range 1-5), but it ignores three schema parameters: to_date, from_date, and lookback_days. These may be important for date filtering, and their absence leaves the tool hard to use correctly for exact-range queries.

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: it lists disclosure receipt numbers (rcept_no) for a stock code. This distinguishes it from siblings like get_disclosure_document (fetches a single document) and search_market_disclosures (searches broadly), and the integration note reinforces its role as a discovery/index step.

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?

Clear context: use this tool when you need a stock-code-driven list of recent disclosure receipt numbers, which can then be passed to downstream tools such as get_disclosure_document, view_disclosure, or check_disclosure_risk. It does not explicitly state when not to use it or name alternatives, but the intended workflow is evident.

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