Skip to main content
Glama
Sign In
dart-search-mcp

dart-search-mcp

by memorise8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_multi_company_indicators

Compare profitability, stability, growth, and activity indicators across multiple companies from Korea's DART system by specifying corporate codes, business year, and report type.

Instructions

DART에서 여러 회사의 주요 재무지표를 한 번에 조회합니다.

여러 회사의 수익성, 안정성, 성장성, 활동성 지표를 비교할 수 있습니다.

Parameters:
    corp_code: DART 고유번호 (쉼표로 구분하여 복수 입력, 예: "00126380,00164779")
    bsns_year: 사업연도 (예: "2024", "2023")
    reprt_code: 보고서코드
        11013=1분기보고서, 11012=반기보고서,
        11014=3분기보고서, 11011=사업보고서(기본값)
    idx_cl_code: 지표분류코드 (빈 문자열이면 전체)
        M210000=수익성지표 (매출총이익률, 영업이익률, 순이익률, ROE, ROA 등)
        M220000=안정성지표 (부채비율, 유동비율, 자기자본비율, 이자보상배율 등)
        M230000=성장성지표 (매출액증가율, 영업이익증가율, 총자산증가율 등)
        M240000=활동성지표 (총자산회전율, 재고자산회전율, 매출채권회전율 등)

Returns:
    다중회사 재무지표 비교 (회사별/지표분류별 지표명, 지표값)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "corp_code": "<corp_code>",
      "bsns_year": "<bsns_year>"
    },
    "name": "get_multi_company_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
corp_codeYes
bsns_yearYes
reprt_codeNo11011
idx_cl_codeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits beyond input/output. It mentions only what the tool does and returns, but lacks information about side effects, authorization requirements, rate limits, or data freshness. The read-only nature is assumed but not stated.

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?

The description is well-structured with a summary, parameter list, and return description. It is front-loaded with the main purpose. While moderately long, it is efficient given the complexity of four parameters and the return value. Minor redundancy could be trimmed.

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

Completeness4/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 and the tool's complexity, the description covers parameters and return info adequately. However, it lacks guidance on when to prefer this over sibling tools (e.g., get_financial_indicators) and does not address error handling or prerequisites, which would enhance completeness.

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

Parameters5/5

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

Schema description coverage is 0%, but the description provides detailed explanations for all 4 parameters, including examples (e.g., '00126380,00164779'), defaults, and enum mappings for reprt_code and idx_cl_code. This adds substantial meaning beyond the bare schema.

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?

The description clearly states it retrieves major financial indicators for multiple companies ('여러 회사의 주요 재무지표를 한 번에 조회합니다'). This specific verb-resource combination and the 'multi_company' in the name distinguish it from single-company counterparts like get_financial_indicators.

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?

The description provides detailed parameter explanations but does not explicitly state when to use this tool versus alternatives (e.g., single-company tools) or include any when-not-to-use guidance. Usage context is implied by the term '여러 회사' but not formalized.

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

Deploy Server

Other Tools