Skip to main content
Glama
anboyu-alt

dart-risk-mcp

by anboyu-alt

find_actor_overlap

Compare acquirers across multiple companies' CB/BW/EB and paid-in capital increases to detect common actors and tag their sources.

Instructions

여러 기업(2~5개)의 CB/BW/EB 인수자 + 유상증자 인수자를 비교해 공통 행위자(세력)를 탐지한다.

DART API 제약상, 분석 대상 기업을 직접 지정해야 한다. "행위자 이름으로 역검색"은 현재 불가능하다.

CB/BW/EB 공시(CB_BW, EB 신호)와 유상증자 공시(3PCA, RIGHTS_UNDER 신호)를 모두 수집해 인수자를 통합 비교하며, 공통 행위자에는 출처 태그(CB / 유상증자)를 표시한다.

무자본 M&A 세력은 인수 시점에 CB를 한 번 박은 뒤 수년에 걸쳐 리픽싱·차환으로 굴리므로, 신규 CB 발행결정 공시는 과거에 몰린다. lookback_years로 조회 윈도우를 넓혀야 단년 창에 안 잡히는 다년 공통 인수자를 포착할 수 있다.

Args: company_names: 비교할 기업명 또는 종목코드 목록 (25개, 예: ["에코프로", "바이오제닉스"]) lookback_years: 조회 기간(년). 기본 1년(하위호환), 15년 범위. watchlist: 저장된 워치리스트 인물명. 지정 시 해당 회사군을 company_names와 합집합으로 분석한다 (manage_watchlist로 관리).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_namesNo
lookback_yearsNo
watchlistNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, description fully discloses data sources (CB_BW, EB, 3PCA, RIGHTS_UNDER), tagging behavior (source tags), constraint on reverse search, and lookback_years behavior along with rationale for widening. Comprehensive.

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?

Description is structured with multiple paragraphs, each adding value, and front-loaded with purpose. Could be slightly more concise, but no redundant information. Well-organized for its length.

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?

Given the presence of an output schema, description doesn't need to detail return values. It covers constraints, usage, behavior, and parameter semantics adequately for a tool of this complexity.

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 0%, but description compensates by explaining all three parameters: company_names (list, 2-5), lookback_years (1-5, default 1), watchlist (combined with company_names). Provides examples. Slightly incomplete on exact format but sufficient.

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?

Description clearly states the verb 'detect common actors' and the resource 'CB/BW/EB investors + paid-in capital increase investors across multiple companies', with specific range 2-5. It distinguishes from sibling tools by its unique cross-company actor overlap analysis.

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?

Provides good guidance: when to use, constraints (direct company specification, no reverse search), and rationale for lookback_years widening. Lacks explicit when-not-to-use or comparison with siblings, but context is clear enough.

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/anboyu-alt/dart-risk-mcp'

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