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

opendart-fss-mcp

by hypn4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

financial_indicators

Read-only

Retrieve financial indicators for multiple companies by specifying business year and report code, supporting up to 20 corporations at once.

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>"
    },
    "name": "financial_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
corp_codeYes고유번호 (쉼표 구분, 최대 20개)
bsns_yearYes사업연도 (YYYY)
reprt_codeYes보고서코드 (11011:사업, 11012:반기, 11013:1분기, 11014:3분기)
idx_cl_codeNo지표분류코드

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds no further behavioral context beyond the purpose. With annotations, a 3 is appropriate.

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 that is concise and front-loaded with the main action. No wasted words, though it could benefit from more structure.

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 is too brief given the complexity of parameters (multiple corp_codes, optional idx_cl_code). It lacks context on how to use these parameters effectively.

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?

Schema coverage is 100% with descriptions for all 4 parameters. The description adds no extra meaning beyond the schema, so baseline 3.

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 'retrieve' and resource 'financial indicators' with scope 'multiple companies.' This distinguishes it from siblings like financial_single_indicators.

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 such as financial_single_indicators. The description only states what it does without usage context.

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