Skip to main content
Glama
jjlabsio

korea-stock-mcp

get_disclosure_list

Filter and retrieve disclosure reports by company code, date range, disclosure type, and more. Supports various sorting and pagination options.

Instructions

공시검색: 공시 유형별, 회사별, 날짜별 등 여러가지 조건으로 공시보고서 검색기능을 제공합니다. 최근 공시를 검색할때는 bgn_de를 반드시 지정하세요.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo정렬 (date: 접수일자, crp: 회사명, rpt: 보고서명) ※ 기본값 : date
bgn_deNo검색시작 접수일자(YYYYMMDD) 1) 기본값 : 종료일(end_de)
end_deNo검색종료 접수일자(YYYYMMDD) 1) 기본값 : 당일
page_noNo페이지 번호(1~n) 기본값 : 1
corp_clsNo법인구분 (Y: 유가증권시장, K: 코스닥, N: 코넥스, E: 기타) ※ 없으면 전체조회, 복수조건 불가
sort_mthNo정렬방법 (asc: 오름차순, desc: 내림차순) ※ 기본값 : desc
corp_codeNo공시대상회사의 고유번호(8자리)
pblntf_tyNo공시유형 // A : 정기공시, B : 주요사항보고, C : 발행공시, D : 지분공시, E : 기타공시, F : 외부감사관련, G : 펀드공시, H : 자산유동화, I : 거래소공시, J : 공정위공시
page_countNo페이지당 건수(1~100) 기본값 : 10, 최대값 : 100
last_reprt_atNo최종보고서 검색여부 (Y 또는 N) 1) 기본값 : N(정정이 있는 경우 최종정정만 검색)
pblntf_detail_tyNo공시상세유형
Behavior2/5

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

No annotations provided, so description must disclose behaviors. It only states the function without mentioning rate limits, authentication, or side effects. The description is minimal.

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?

Two sentences, front-loaded with purpose, no redundant information. Every sentence earns its place.

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 11 parameters, no output schema, and no annotations, the description should provide more context about return format, pagination, or error handling. It only covers basic purpose and one use case.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. The description adds semantic value by stating that bgn_de is mandatory for recent searches, which goes beyond the schema's optional default.

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 clearly states the tool searches for disclosure reports by various conditions. It is distinct from siblings like get_financial_statement or get_stock_base_info, but does not differentiate from the similarly named get_disclosure tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides one specific guideline: 'When searching recent disclosures, you must specify bgn_de.' This is helpful but does not cover when not to use or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jjlabsio/korea-stock-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server