Skip to main content
Glama
edinet-mcp

edinet-mcp

by koizumikento

get_filing_document

Read-onlyIdempotent

Download a Japanese regulatory filing as a PDF or CSV ZIP using its document ID; use the CLI for files larger than 2 MiB.

Instructions

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

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": {
      "document_id": "<document_id>"
    },
    "name": "get_filing_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNopdf
document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context in the 2 MiB payload ceiling and the CLI workaround, which is exactly the kind of operational constraint an agent needs. It stops short of saying whether oversize requests error out or truncate, keeping it from a 5.

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 short sentences, zero filler, with the core action stated first and the operational caveat second. Every sentence carries distinct information.

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?

With no output schema, the description must convey the return value, and it does: a PDF or CSV ZIP for the given filing. The size limit and CLI alternative cover the main operational risk. The only meaningful omission is failure behavior above 2 MiB and how to discover a valid document_id.

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 0%, so the description must carry parameter meaning, and it does so only partially: 'by ID' clarifies document_id's role and 'PDF or CSV ZIP' confirms the format enum selects the archive type. It does not explain the ID's expected shape (the schema's ^[A-Z0-9]{8}$ pattern) or where an agent obtains one, leaving a gap given the lack of parameter descriptions.

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?

The description states a specific verb and resource ('Retrieve a filing's PDF or CSV ZIP') plus the lookup key ('by ID'), so the agent knows exactly what the tool returns. It does not explicitly contrast with the sibling list_filings, though the verb difference (retrieve one vs. list) makes the distinction reasonably clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is one concrete usage rule — 'Use the CLI for files over 2 MiB' — which tells the agent when this tool is unsuitable. However, it offers no guidance relative to the sibling list_filings (e.g., how to obtain a document_id) and no fallback description of what happens if the file exceeds the limit when called anyway.

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