MyDART

by kr.eocpa

Overview Discussions Admin

get_going_concern

Read-onlyIdempotent

MyDART MCP의 get_going_concern 도구는 계속기업 위험을 정량 재무지표와 감사보고서 기재의 교차로 판정합니다.

[Purpose]

계속기업: 정량 징후 × 감사보고서 기재 대조 — a mismatch is a cue to read the 원문, not a finding.
Lists: search_audit_findings; figures: get_financials; 문단 원문: get_audit_report.

[Usage]

"이스타코 2024 계속기업 위험 있어?" → corp="이스타코", year=2024
"별도 기준 정량 점검" → corp="…", year=2024, fs_div="OFS"

[Response]

flags.consecutive_op_loss = NUMBER of 연속 영업손실 years (not a bool); others bool|null.
grade: 판정불가(no data)/양호(0)/주의(1~~2)/경계(3~~4)/위험(5+)
cross_check.code: both/quant_only/text_only/none/insufficient_data/quant_unavailable/report_unavailable
text: audit_opinion, evidence_source, report_fs_div

[Rules]

going_concern_mentioned false = parser found no GC text, not proof of none; null = report not secured. quant_only covers both cases.
한정/부적정/의견거절: GC matters can sit in 의견근거 — read it (cross_check.next_step).
grade "판정불가" is not "양호". flags null = account not secured, not false.
fs_div (figures) is post-fallback — CFS may return OFS.

Input Schema

Name	Required	Description
`corp`	Yes	회사명/종목코드/corp_code
`year`	Yes	결산 사업연도 (회계연도·fiscal year), NOT the 공시(제출)연도 — pass the user's year as-is, never subtract: '2025 사업보고서' → 2025. Convert ONLY when the user explicitly names the 공시연도: '2026년에 공시된 사업보고서' → 2025. Relative ('최근 N개년'·'작년'): count back from the latest PUBLISHED 사업연도 (사업보고서 filed ≤90 days after 결산기말) — for 12월 결산 last year from April, the year before last in Jan~Mar (e.g. if latest = FY2025 → 최근 5개년 = 2021~2025). 비12월 결산 (3·6·9월): the year its 결산기 STARTS (3월 결산 2025-04~2026-03 = 2025; get_financials calls it 2026).
`fs_div`	No	Default CFS (연결); OFS = 별도. No 연결 → auto fallback to 별도 (response fs_div = basis used).
`refresh`	No	Bypass cache; re-collect

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 15, 2026

changedInput schema / properties / fs_div / description

Previous value: -"연결(CFS)/별도(OFS), default CFS. Falls back to 별도 automatically when 연결 is absent (the response fs_div reports the basis actually used). Aliases consolidated/separate·연결/별도 also accepted (case·spaces ignored)."New value: +"Default CFS (연결); OFS = 별도. No 연결 → auto fallback to 별도 (response fs_div = basis used)."

changedInput schema / properties / refresh / description

Previous value: -"Bypass the cache and re-collect"New value: +"Bypass cache; re-collect"

changedInput schema / properties / year / description

Previous value: -"결산 사업연도 (회계연도, fiscal year) — the number you pass IS the 사업연도=회계연도=결산연도. Do NOT subtract it; pass it as-is. Only tools where year is optional auto-select the latest published year when omitted (if year is required in the tool you are calling, it cannot be omitted — confirm the year actually used via the response `year` field).e.g. 'FY2025'·'2025년 재무제표'·'2025 사업보고서'·'2025 회계연도' → all 2025 (결산일 2025-12-31). Convert ONLY when the user explicitly names the 공시(제출)연도, as in '○○년에 공시된 보고서': a 12월 결산법인 files by the end of March of the following year.(e.g. '2026년에 공시된 사업보고서' → 2025). Otherwise the input is ALWAYS on a 사업연도=회계연도=결산연도 basis. Relative expressions ('최근 N개년'·'작년' and the like) count back from the most recent PUBLISHED 사업연도 as of today: a 사업보고서 is filed within about 90 days after 결산 (12월 결산 법인 → March of the following year), so from April the latest is last year, and in Jan~Mar it is the year before last. e.g. if today is 2026-06 the latest is FY2025 → '최근 5개년'=2021~2025 (NOT 2020~2024). Supported floor is FY2015 (the range OpenDART's structured APIs cover) — 2014 and earlier are rejected. A 비12월 결산 (3·6·9월) 법인 may have its latest 사업연도 equal to the calendar year (e.g. a 3월 결산 company from July onward)."New value: +"결산 사업연도 (회계연도·fiscal year), NOT the 공시(제출)연도 — pass the user's year as-is, never subtract: '2025 사업보고서' → 2025. Convert ONLY when the user explicitly names the 공시연도: '2026년에 공시된 사업보고서' → 2025. Relative ('최근 N개년'·'작년'): count back from the latest PUBLISHED 사업연도 (사업보고서 filed ≤90 days after 결산기말) — for 12월 결산 last year from April, the year before last in Jan~Mar (e.g. if latest = FY2025 → 최근 5개년 = 2021~2025). 비12월 결산 (3·6·9월): the year its 결산기 STARTS (3월 결산 2025-04~2026-03 = 2025; get_financials calls it 2026)."

Changed1 schema field changedOct 12, 2026

changedInput schema / properties / fs_div / description

Previous value: -"연결(CFS)/별도(OFS), default CFS. Falls back to 별도 automatically when 연결 is absent (the response fs_div reports the basis actually used). Aliases consolidated/separate·연결/별도 also accepted."New value: +"연결(CFS)/별도(OFS), default CFS. Falls back to 별도 automatically when 연결 is absent (the response fs_div reports the basis actually used). Aliases consolidated/separate·연결/별도 also accepted (case·spaces ignored)."

Changed1 schema field changedAug 14, 2026

changedInput schema / properties / fs_div / description

Previous value: -"연결(CFS)/별도(OFS), default CFS. Falls back to 별도 automatically when 연결 is absent. Aliases consolidated/separate·연결/별도 also accepted."New value: +"연결(CFS)/별도(OFS), default CFS. Falls back to 별도 automatically when 연결 is absent (the response fs_div reports the basis actually used). Aliases consolidated/separate·연결/별도 also accepted."

Changed3 schema fields changedAug 13, 2026

changedInput schema / properties / fs_div / description

Previous value: -"연결(CFS)/별도(OFS), 기본 CFS. 연결 없으면 별도 자동 폴백. consolidated/separate·연결/별도 별칭도 허용."New value: +"연결(CFS)/별도(OFS), default CFS. Falls back to 별도 automatically when 연결 is absent. Aliases consolidated/separate·연결/별도 also accepted."

changedInput schema / properties / refresh / description

Previous value: -"캐시 무시하고 강제 재수집"New value: +"Bypass the cache and re-collect"

changedInput schema / properties / year / description

Previous value: -"결산 사업연도(회계연도, fiscal year) — 입력한 숫자가 곧 사업연도=회계연도=결산연도다. 빼지 말고 그대로 넣는다. year 가 선택 입력인 도구만 생략 시 최신 공시 연도를 자동 지정한다(이 도구에서 year 가 required 면 생략 불가 — 실제 사용 연도는 응답 year 필드로 확인).예: 'FY2025'·'2025년 재무제표'·'2025 사업보고서'·'2025 회계연도' → 모두 2025(결산일 2025-12-31). 환산은 사용자가 '○○년에 공시(제출)된 보고서'처럼 공시(제출)연도를 명시한 경우에만 수행: 12월 결산법인은 익년도 3월말까지 공시함.(예: '2026년에 공시된 사업보고서' → 2025). 그 밖에는 항상 입력값은 사업연도=회계연도=결산연도 기준. 상대표현('최근 N개년'·'작년' 등)은 '오늘' 기준 가장 최근 '공시된' 사업연도부터 역순으로 센다: 사업보고서는 결산 후 약 90일 내(12월 결산 법인 → 익년 3월) 공시되므로 4월 이후면 최신=작년, 1~3월이면 최신=재작년. 예: 오늘이 2026-06이면 최신=FY2025 → '최근 5개년'=2021~2025 (2020~2024 아님). 지원 하한 FY2015(OpenDART 정형 API 제공 범위) — 2014 이하는 거부된다. 비12월 결산(3·6·9월) 법인은 최신 사업연도가 달력연도와 같을 수 있다(예: 3월 결산은 7월부터 당해연도)."New value: +"결산 사업연도 (회계연도, fiscal year) — the number you pass IS the 사업연도=회계연도=결산연도. Do NOT subtract it; pass it as-is. Only tools where year is optional auto-select the latest published year when omitted (if year is required in the tool you are calling, it cannot be omitted — confirm the year actually used via the response `year` field).e.g. 'FY2025'·'2025년 재무제표'·'2025 사업보고서'·'2025 회계연도' → all 2025 (결산일 2025-12-31). Convert ONLY when the user explicitly names the 공시(제출)연도, as in '○○년에 공시된 보고서': a 12월 결산법인 files by the end of March of the following year.(e.g. '2026년에 공시된 사업보고서' → 2025). Otherwise the input is ALWAYS on a 사업연도=회계연도=결산연도 basis. Relative expressions ('최근 N개년'·'작년' and the like) count back from the most recent PUBLISHED 사업연도 as of today: a 사업보고서 is filed within about 90 days after 결산 (12월 결산 법인 → March of the following year), so from April the latest is last year, and in Jan~Mar it is the year before last. e.g. if today is 2026-06 the latest is FY2025 → '최근 5개년'=2021~2025 (NOT 2020~2024). Supported floor is FY2015 (the range OpenDART's structured APIs cover) — 2014 and earlier are rejected. A 비12월 결산 (3·6·9월) 법인 may have its latest 사업연도 equal to the calendar year (e.g. a 3월 결산 company from July onward)."

First observedAug 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower; the description nonetheless adds real behavior: grade banding semantics, cross_check code enumeration, the fact that consecutive_op_loss is a count not a bool, and null/False distinctions. It stops short of describing latency, caching depth, or pagination, so not a full 5.

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?

Front-loads the one-line purpose and organizes the rest into [Purpose]/[Usage]/[Response]/[Rules], so an agent can scan to the section it needs. It is dense and long, and a few rules restate response fields already listed above, but no section is filler.

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?

No output schema exists, so the description carries the return-value burden and does so: it enumerates flags, grade bands, cross_check codes, and text fields, and it documents the parser pitfall (going_concern_mentioned false vs null) that would otherwise cause misreads. For a 4-param analytical tool with a rich response, nothing material is missing.

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 description coverage is 100%, which normally sets the baseline at 3, but the description adds a semantic the schema omits: fs_div is post-fallback, so a CFS request may return OFS figures in the response. That is a genuine cross-field nuance beyond the schema text.

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 analytical action (judging going-concern risk by intersecting quantitative metrics with audit-report text) rather than a generic resource operation. It explicitly names the sibling tools it draws on (search_audit_findings, get_financials, get_audit_report), letting an agent place it among the 14 siblings without opening schemas.

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

Usage Guidelines5/5

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

The [Usage] section gives concrete when-to-use examples ('이스타코 2024 계속기업 위험 있어?' → corp/year; 별도 기준 → fs_div=OFS) and the [Purpose] block routes the agent to alternatives for lists, figures, and report text. It also warns that a mismatch is a cue to read the 원문, not a finding — explicit guidance on interpretation, not just invocation.

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

All MyDART 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?