Skip to main content
Glama
Sign In

kabuken

by io.github.Intellics-ai
OverviewDiscussionsAdmin

Screen companies

screen_companies
Read-only

Find Japanese listed companies matching financial ratio filters (ROE, ROA, operating margin and others). Supported ratios: roe, roa, operating_margin (fractions, e.g. 0.15 means 15%), current_ratio and debt_to_equity (plain ratios, e.g. 1.5 means 1.5x). Multiple filters are combined with AND logic. Only the latest reported period per company is considered. Companies with negative equity are excluded by default. Banks, insurers and securities firms (statement_format bank, insurance, insurance_life, insurance_nonlife or securities, read from each filing whatever its accounting standard) are excluded by default, because their ratios measure a balance sheet that is the business itself and have no operating margin or current ratio; include_financials: true includes them. ROE and ROA divide net income by the average of the opening and closing balance (the 決算短信 convention); roe_basis and roa_basis are "average", or "year_end" when the opening balance is not available. Companies no longer on the JPX listed-company list are excluded by default; include_delisted: true includes them. Each result carries its statement_format. Source: EDINET (https://disclosure2.edinet-fsa.go.jp/), PDL 1.0 (https://www.digital.go.jp/resources/open_data/public_data_license_v1.0). Data is processed by Kabuken, not raw unprocessed FSA data. Figures are calculated by Kabuken from EDINET filings, not reported directly by EDINET. Not investment advice.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1-100, default 20)
cursorNoOpaque next_cursor from the previous response; send it with the same filters, sort and limit to get the next page. total is returned on the first page only.
filtersYesArray of ratio filters. Each filter specifies a metric, a comparison operator (gt, lt, gte, lte), and a numeric threshold value.
sort_byNoOptional metric to sort results by. Default sort is by entity_code.
industry_idNoOptional industry filter. Industry ID, e.g. ind_3700. The bare industry code (3700) is also accepted.
sort_directionNoSort direction when sort_by is specified. Default: desc.
include_delistedNoInclude companies that are no longer on the JPX listed-company list (delisted), which are excluded by default. Default: false.
include_financialsNoInclude banks, insurers and securities firms, which are excluded by default. Their ROE, ROA and debt_to_equity are not comparable with other companies', and operating_margin and current_ratio are null for banks and insurers. Default: false.
exclude_negative_equityNoExclude companies with negative equity (inferred from a negative debt_to_equity ratio, since liabilities are never negative) from results. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque next_cursor from the previous response; send it with the same filters, sort and limit to get the next page. total is returned on the first page only.",
+  "maxLength": 512,
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the safe read-only annotations, the description discloses default exclusions (negative equity, financials, delisted), rationale for excluding financials, latest-period behavior, ROE/ROA averaging conventions, and data provenance. This is unusually rich behavioral context for invoking the tool correctly.

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?

The description is front-loaded and dense with relevant information; most sentences earn their place, including the ratio conventions and exclusion rules. It is a long single paragraph, but the length is largely justified by the complexity of the screening semantics and provenance requirements.

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 the rich input schema and safe annotations, the description covers the main invocation semantics: filters, defaults, exclusions, ratio computation, and source caveats. It is somewhat thin on the shape of returned company records, but the critical screening behavior is well specified.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaningful semantics beyond the schema: filter AND logic, ratio units, latest-reported-period treatment, negative-equity default, financials inclusion rationale, and ROE/ROA basis. It does not explain every parameter, but it covers the critical screening behavior.

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 states a specific verb and resource: finding Japanese listed companies matching financial ratio filters. It names the supported ratios and scope, so an agent can distinguish it from lookup tools like get_company or search_companies.

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 clear that this tool is for ratio-based screening with AND-combined filters and explains several default-inclusion decisions. It does not explicitly route the agent away from siblings such as search_companies or compare_companies, so it lacks full when-not guidance.

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

All kabuken toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources