Skip to main content
Glama
edinet-mcp

edinet-mcp

by koizumikento

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EDINET_API_KEYYesEDINET API key issued according to EDINET's guide; replace YOUR_EDINET_API_KEY with your own setting.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_filingsB

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

get_filing_documentA

Retrieve a filing's PDF or CSV ZIP by ID. Use the CLI for files over 2 MiB.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are clearly distinct: list_filings discovers filings, while get_filing_document retrieves the actual PDF/CSV for a known ID. There is no overlap or risk of misselection.

Naming Consistency5/5

Both tools follow a consistent snake_case verb_noun pattern (list_filings, get_filing_document). The convention is predictable and readable.

Tool Count3/5

Two tools is on the thin side for a filing-data domain; discovery and retrieval are covered but remain a minimal surface. It is borderline rather than mismatched.

Completeness3/5

The core list-then-fetch workflow is covered, but there is no metadata lookup for a single filing, no search by company/ticker or date range, and no way to enumerate document types. Agents needing richer queries would hit dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues