Skip to main content
Glama
Sign In

kabuken

by io.github.Intellics-ai
OverviewDiscussionsAdmin

Get segment breakdown

get_segment_breakdown
Read-only

Return segment data (by business segment, geography or consolidation scope) from one EDINET filing of a Japanese listed company. Shows how facts are broken down by business segment, geography, or reporting consolidation scope. Includes bilingual axis and member labels; a label can be null when the filing's taxonomy has none. Also returns regional revenue and non-current assets parsed from the filing's geographic table, each row with its source cell and a reconciliation status; rows with is_corporate_elim true are corporate or elimination lines, not regions. 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. Includes EDINET Taxonomy content, excluded from PDL 1.0 and separately licensed (https://www.fsa.go.jp/search/EDINET_Taxonomy_Legal_Statement.html). © Copyright 2014 Financial Services Agency, The Japanese Government. When truncated is true, next_cursor is set; pass it as cursor to read the remaining segment rows (next_cursor is null on the last page). The geographic table is returned on the first page only. Not investment advice.

Input Schema

NameRequiredDescriptionDefault
viewNo'segments' returns the dimension segments only, 'geographic' returns the regional table rows only, 'all' returns both. Default all.all
limitNoMaximum number of segment records to return per page (1-500, default 100)
cursorNoOpaque next_cursor from the previous response; send it with the same doc_id, fact_name, include_all_axes, view and limit to get the next page. The geographic table is returned on the first page only.
doc_idYesEDINET document ID, e.g. S100ABCD
fact_nameNoOptional XBRL dimension axis name to filter results to a specific axis (e.g. 'jppfs_cor:ConsolidatedOrNonConsolidatedAxis'). If omitted, only business segment, geographic and consolidation scope axes are returned, business segments first.
include_all_axesNoWhen true, also returns non-segment axes such as components of equity, officers and share classes (listed after the segment axes). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque next_cursor from the previous response; send it with the same doc_id, fact_name, include_all_axes, view and limit to get the next page. The geographic table is returned on the first page only.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of segment records to return (1-500, default 100)"New value: +"Maximum number of segment records to return per page (1-500, default 100)"
  2. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already cover the safe read profile, and the description adds substantial behavioral context on top: null labels when the taxonomy lacks them, per-row source cell and reconciliation status for geographic rows, the is_corporate_elim flag meaning rows are not real regions, and that the geographic table appears only on page one. Data provenance (Kabuken processing, EDINET Taxonomy carve-out and licensing) is also disclosed, which matters for redistribution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The functional purpose is correctly front-loaded, but roughly a third of the text is licensing and copyright boilerplate that dilutes the operational content an agent needs. The remaining sentences are dense but mostly 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?

With no output schema, the description carries the burden of explaining return values, and it does so well: segment dimension rows, bilingual labels with possible nulls, geographic rows with reconciliation status, and pagination via truncated/next_cursor. A short note on the shape of the segment record fields would make it fully self-sufficient.

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%, so the baseline is 3. The description mostly restates what the schema already states (cursor reuse, geographic-on-first-page) and adds little parameter-level meaning beyond the schema, such as how axis ordering interacts with fact_name filtering.

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?

States a specific verb and resource ('Return segment data ... from one EDINET filing') and enumerates the three breakdown types plus the geographic table, so the agent knows exactly what content comes back. It does not name or contrast with any sibling (e.g. get_financial_facts, get_calculation_tree), so it falls short of the 5 bar for explicit sibling differentiation.

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?

Usage is implied by the scope ('one EDINET filing'), and the truncation/cursor paragraph gives concrete guidance on continuing a paginated read. However, nothing says when to prefer this over get_financial_facts or get_document_summary, and there are no stated exclusions or prerequisites.

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