Skip to main content
Glama
Sign In
EDINET DB MCP Server

EDINET DB MCP Server

by edinetdb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search_shareholders

Find all listed companies where an investor or fund has filed a large-shareholding report. Enter a partial name (Japanese or English) to reverse-search from holder to issuers.

Instructions

Look up an investor by name and get every listed company where it has filed a large-shareholding report. This is the reverse of get_shareholders: start from the holder, not the issuer.

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": {
      "q": "<q>"
    },
    "name": "search_shareholders"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesInvestor or fund name, partial match. Japanese or English, e.g. 'ブラックロック'.
limitNoMaximum results (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral disclosure. It clearly communicates that the operation is a lookup/search of filing relationships, but it does not mention pagination, default result count, or any output structure. Core behavior is present; depth is minimal.

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 concise sentences with the core action in the first sentence and the key differentiator in the second. No filler or redundant restatement.

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?

Simple 2-parameter tool with fully documented schema and a clear relationship to its sibling. The description covers the main concept and reverse relationship; only a return-shape note would make it fully complete, but this is a minor gap.

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%, with q and limit already documented including example and default. The description adds no new parameter meaning beyond the schema, so baseline 3 applies.

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 ('Look up'), the resource (investor by name), and the outcome (every listed company with a large-shareholding filing). It also names the sibling it is the reverse of, so it is immediately distinguishable from get_shareholders.

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

Usage Guidelines5/5

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

Explicitly frames the tool as the reverse of get_shareholders and tells the agent to start from the holder rather than the issuer. This is a clear when-to-use signal and references the main alternative.

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