EDINET DB MCP Server

get_financials

Retrieve multi-year financial statements for a Japanese company — revenue, operating income, net income, assets, equity, and cash flow — directly from EDINET XBRL filings.

Instructions

Get the multi-year financial statement time series for one company — revenue, operating income, net income, assets, equity and cash flow per period. Figures come from XBRL in the company's own regulatory filings; no language model is involved in producing them.

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": {
      "code": "<code>"
    },
    "name": "get_financials"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	EDINET code of the company, e.g. E02144 (Toyota Motor) or E02367 (Nintendo). This is not the securities code — resolve a name or securities code to an EDINET code with search_companies first.
`years`	No	Number of most recent years to return. Omit for the full history.
`period`	No	annual (default) = fiscal-year figures from annual securities reports. quarterly = year-to-date cumulative figures. quarterly_standalone = the discrete quarter on its own.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does meaningful work: it states the data source ('XBRL in the company's own regulatory filings') and explicitly guarantees no language model is involved in producing figures. This gives the agent confidence about provenance, though it does not describe output structure or failure behavior.

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 two sentences with no wasted words. The first sentence front-loads the action, scope, and content; the second adds valuable provenance context. Both sentences earn their place.

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?

Given there is no output schema, the description compensates by listing the key line items and stating the time-series nature. It does not detail row layout or units, but the information is sufficient for an agent to invoke the tool correctly and set expectations for the response.

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%, and the schema already explains `code`, `years`, and `period` in detail, including the EDINET-code caveat and period meanings. The description adds no parameter-level meaning beyond framing the result as a per-period time series, so baseline 3 is appropriate.

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 uses a specific verb ('Get') with a clear resource ('multi-year financial statement time series') and scope ('for one company'), and it lists the exact metrics returned. This makes it easy to distinguish from siblings like get_earnings or get_segments without opening their schemas.

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?

The description makes it clear this is for retrieving broad financial-statement time series for a single company, which gives the agent useful context for when to select it. It does not explicitly name alternatives or state when not to use it, so it stops short of full routing guidance.

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

Deploy Server