Skip to main content
Glama
Sign In
edinet-util-mcp-server

edinet-util-mcp-server

by gotoai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

export_filing

Idempotent

Download an EDINET filing by doc_id and save it as Markdown files—index, key figures, and section files—returning the output folder and file list; existing exports are reused without re-downloading.

Instructions

Download one filing by doc_id and save it as Markdown files in the EDINET output folder: index.md (metadata and contents), figures.md (5-year key figures) and one file per section. Returns the folder and file list; read the files you need. A filing already exported is returned without downloading again.

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": {
      "doc_id": "<doc_id>"
    },
    "name": "export_filing"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesThe filing's doc_id, e.g. S100Y8NY.
refreshNoDownload and convert again.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the write-like side effects of saving Markdown files in the EDINET output folder, the exact filenames produced, and the no-redownload behavior for existing exports. It does not cover permissions, rate limits, or failure modes, but it adds substantial behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three focused sentences with no wasted wording. It is front-loaded with the core action and output, then adds the return shape and caching behavior.

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?

The description is complete for this tool: it covers the download-and-convert action, output files, return value, and caching. An output schema exists, so it does not need to explain return values in more detail.

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 description coverage is 100%, so the parameter meanings are already fully documented. The description reinforces that doc_id selects one filing, but it does not add meaning for the refresh parameter, which is relevant because refresh overrides the stated no-redownload behavior.

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 states a specific verb and resource: download one filing by doc_id and save it as Markdown files. It distinguishes the operation from list_filings by emphasizing one filing and identifying the resulting index.md, figures.md, and section files.

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?

It clearly indicates when to use the tool: to export a single filing and then read the generated files. It also explains caching behavior for already-exported filings, though it does not explicitly compare against list_filings or describe when not to use it.

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