Skip to main content
Glama
Sign In
opendart-fss-mcp

opendart-fss-mcp

by hypn4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

financial_single_indicators

Read-only

Retrieve financial indicators for a single Korean corporation from the DART system. Input the company code, business year, report type, and indicator classification to obtain specific metrics.

Instructions

단일 기업의 재무 지표를 조회합니다.

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>",
      "reprt_code": "<reprt_code>",
      "idx_cl_code": "<idx_cl_code>"
    },
    "name": "financial_single_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
corp_codeYes고유번호 (8자리)
bsns_yearYes사업연도 (YYYY)
reprt_codeYes보고서코드 (11011:사업, 11012:반기, 11013:1분기, 11014:3분기)
idx_cl_codeYes지표분류코드

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. Description does not add additional behavioral context such as data freshness, required parameter details, or what 'indicators' means. Minimal added value beyond annotations.

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?

Single sentence is concise and front-loaded with the core action. However, it lacks any structural elements like bullet points or examples that could improve usability.

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?

Despite having an output schema, the description does not explain what financial indicators are returned or how to interpret results. For a tool with 4 required parameters and many siblings, more context is needed for effective use.

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

Parameters3/5

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

All parameters have descriptions in the input schema (100% coverage). The tool description does not add extra meaning or format constraints beyond what schema already provides, meeting the baseline.

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 it retrieves financial indicators of a single company. Verb '조회' (retrieve) and resource '재무 지표' (financial indicators) are specific. Among siblings, it distinguishes from multi-entity and full statement tools.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like financial_indicators or financial_multi_account. The description implies single-company use but doesn't explicitly state when not to use or provide criteria for selection.

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