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

opendart-fss-mcp

by hypn4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

event_default_occurrence

Read-only

Query corporate default events by corporation code and date range. Obtain default occurrence data from Korea's DART disclosure system for financial analysis.

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

Input Schema

NameRequiredDescriptionDefault
corp_codeYes고유번호 (8자리)
bgn_deNo시작일 (YYYYMMDD)
end_deNo종료일 (YYYYMMDD)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds no behavioral details beyond 'inquires,' but annotations cover the safety profile adequately.

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 a single concise sentence without redundancy. However, it could benefit from slight expansion for clarity.

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?

With an output schema provided, return values are documented. The description, while minimal, covers the basic purpose. No critical gaps given the tool's simplicity.

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% and already describes parameters (corp_code, dates). The description adds no parameter-level meaning, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '채무불이행을 조회합니다.' (Inquires about default) identifies the resource as default but is vague; it doesn't specify what type of default (e.g., debt default) or that it queries occurrences.

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 usage context is provided. There are many sibling event tools (e.g., event_merger_decision) with no guidance on when to use this tool over others.

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