edinet-util-mcp-server

Overview Schema Source Related Servers Discussions Admin

list_filings

Read-only

Lists EDINET filings submitted between two dates, with optional filters for company or document type, and returns each filing's doc_id for export_filing.

Instructions

List EDINET filings submitted between two dates (at most 31 days, about 1 second per day), optionally only one company's or only some document types. Returns each filing's doc_id for export_filing, newest first.

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": {
      "from_date": "<from_date>"
    },
    "name": "list_filings"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`to_date`	No	Last submission date, YYYY-MM-DD; default from_date.
`sec_code`	No	Only this securities code, e.g. 7203.
`doc_types`	No	Document type codes, e.g. ['120', '160'].
`from_date`	Yes	First submission date, YYYY-MM-DD.
`filer_name`	No	Only filers whose name contains this.
`edinet_code`	No	Only this filer, e.g. E02144.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only and open-world semantics, and the description adds real operational context beyond them: a hard 31-day maximum window, roughly one second of latency per day queried, and newest-first ordering. It does not say whether results are truncated at the limit, which is the one behavioral gap.

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?

Two dense sentences: the operation and its date-span cost come first, then the filters, then the return value and ordering. No filler and nothing redundant with the schema.

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?

An output schema exists, so return values need not be spelled out, yet the description still flags doc_id and newest-first ordering, which is helpful. The remaining gap is whether the limit parameter silently truncates results, which matters for a paginated-listing tool.

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

Parameters4/5

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

Schema coverage is 86%, so the schema carries most parameter meaning and the baseline would be 3. The description still adds the non-obvious 31-day span constraint on from_date/to_date, which appears nowhere in the schema, plus the framing that all filter parameters are optional.

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?

States a specific verb and resource ('List EDINET filings'), scopes it by date range, and names the downstream consumer of the returned doc_id (export_filing). An agent can distinguish this from export_filing without opening either schema.

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?

Explains that filters are optional and singles out the two filter modes (one company, some document types), which implies when to narrow vs list broadly. It stops short of explicitly saying when to prefer a sibling tool, though the doc_id/export_filing handoff effectively routes the agent.

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

Deploy Server