Skip to main content
Glama

MyDART

by kr.eocpa
OverviewDiscussionsAdmin

find_corp_code

Read-onlyIdempotent

MyDART MCP의 find_corp_code 도구는 회사명·종목코드로 DART 법인 식별자(corp_code)의 후보를 확인합니다.

[Purpose]

  • IMPORTANT: first call when a company's corp_code is unknown.

  • Also to disambiguate same-named companies.

  • ID resolution only — 업종·data location: get_company_profile; disclosure listings: search_disclosures.

[Usage]

  1. "카카오" → corp_code 획득 → 재무제표 조회(get_financials)

  2. "삼성전자" → corp_code 획득 → 임원 현황 조회(get_periodic_report)

  3. "'동양' 들어가는 회사 후보 보여줘" → query="동양", limit=20

  4. "005930이 어느 회사야?" → query="005930"

[Response]

  • stock_code: present = listed (common shares); empty/absent = unlisted.

  • count = rows returned (capped by limit), not the total match count. 0 hits adds notes.

[Rules]

  • results is a similarity-ranked candidate array — do not assume the first item is the answer.

  • corp_code identifies the DART LEGAL ENTITY CODE, not the listing ticker. 우선주 codes map to the 보통주 issuer; ETF/ETN codes have no mapping.

  • Common names may overflow the default limit — raise it when candidates look truncated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax candidates to return (default 10, max 50)
queryYes회사명 (한/영), 6-char 종목코드 (digits or alphanumeric like 0126Z0), or 8-digit corp_code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"회사명 (한/영), 6-digit 종목코드, or 8-digit corp_code"New value: +"회사명 (한/영), 6-char 종목코드 (digits or alphanumeric like 0126Z0), or 8-digit corp_code"
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max candidates to return"New value: +"Max candidates to return (default 10, max 50)"
  3. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"최대 반환 개수"New value: +"Max candidates to return"
    • changedInput schema / properties / query / description
      Previous value: -"회사명(한/영), 6자리 종목코드, 또는 8자리 corp_code"New value: +"회사명 (한/영), 6-digit 종목코드, or 8-digit corp_code"
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing that results is a similarity-ranked candidate array (first item is not necessarily the answer), that count is capped by limit rather than total matches, that 0 hits adds notes, and that preferred-share codes map to the common-share issuer while ETF/ETN have no mapping.

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-loaded with the critical 'first call' rule and organized under Purpose/Usage/Response/Rules headings that make scanning fast. Slightly verbose due to the bilingual restatement in the opening line, but no sentence is wasted.

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, yet the description explains the meaningful response fields (stock_code presence, count semantics, notes on zero hits) and the corp_code-vs-ticker distinction. Nothing an agent needs to call and interpret this correctly 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 coverage is 100% and already documents query formats and limit bounds, but the description adds real meaning: when to raise limit (common names overflow the default) and that count reflects the capped rows. This compensates for the non-obvious semantic that limit silently truncates candidates.

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+resource (회사명·종목코드 → corp_code 후보 확인) and explicitly routes ID-resolution away from siblings get_company_profile and search_disclosures. An agent can distinguish it from every sibling without opening a schema.

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?

Explicitly declares itself the first call when corp_code is unknown, gives the disambiguation case, and lists four worked examples mapping user phrasing to query values. Alternatives (get_company_profile, search_disclosures, get_financials, get_periodic_report) are named with their conditions.

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

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