Skip to main content
Glama
edinet-mcp

edinet-mcp

by koizumikento

list_filings

Read-onlyIdempotent

Retrieve EDINET filing records for a specified date, with optional filters for filer and document type to narrow regulatory filing results.

Instructions

List EDINET filing records for a date, filtered by filer or document type.

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

Input Schema

NameRequiredDescriptionDefault
filerNo
limitNo
offsetNo
filing_dateYes
document_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered and the description is not obligated to restate it. The description adds the filtering dimensions (filer, document type) but says nothing about pagination behavior, result ordering, or rate limits on this open-world external source.

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?

A single information-dense sentence with the resource and the two filter axes front-loaded and no filler. It is arguably too terse for a five-parameter tool, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema relieves the description of explaining return values, and annotations cover safety. However, with five parameters at 0% schema coverage, an open-world external data source, and no pagination or code-format guidance, the definition leaves gaps an agent would hit on the first call.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry all parameter meaning, yet it explains only three of five parameters (filing_date, filer, document_type) and only in vague terms. It never reveals the YYYY-MM-DD date format, the 3-digit document-type code pattern, or that limit/offset govern paging — all of which remain opaque without a schema description.

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

Purpose4/5

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

States a specific verb ('List') and resource ('EDINET filing records') plus scope ('for a date, filtered by filer or document type'). An agent can grasp the operation immediately, though the description never distinguishes it from the sibling get_filing_document, which requires inferring the difference from the name alone.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of the alternative get_filing_document for retrieving a single document. The only hint at context is the implicit 'query by date' framing, which leaves the agent to infer that this is for enumerating filings rather than fetching one.

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