Skip to main content
Glama

Statements and notes

akkru_statements
Read-onlyIdempotent

Whole statements and notes of one filing, as filed: every row with its value, period, unit and source.

  • get: one statement or note, named by exactly one of statement_type, role_label or block_index. statement_type takes the five main statements by name, for US filings. role_label takes any statement or note by the name the filer gave it, in any filing. block_index takes the position that list shows. 28 credits; 48 when role_label is matched to a differently worded name.

  • list: every statement and note block of the filing with its block_index, statement_type and role_label. 10 credits. Name the filing with filing_id, or with ticker and fiscal_year.

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": {
      "action": "<action>"
    },
    "name": "akkru_statements"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhat to do; each action is described in the tool description.
detailNoResponse detail, same price at every level: "full" (default) returns everything; "light" leaves out the bulkiest fields, such as breakdown lists; "minimal" returns only the values and what identifies them, without sources or calculation details. Every action takes it; a call without detail levels ignores it. Try "light" or "minimal" for shorter replies that use less context and fewer tokens.
tickerNo(get, list) Company ticker, e.g. "AAPL" (US), "000100" (Korea), "1332" (Japan), "VIRI_F" (Europe), "600519_CN" (China A-share); any symbol the company has traded under.
quarterNo(get, list) "FY", "Q1", "Q2", "Q3" or "Q4". Needed only when the fiscal year has several filings of the form; the error then lists the quarters on file.
filing_idNo(get, list) Filing id from akkru_filings action "list". Name the filing with filing_id, or with ticker and fiscal_year, not both.
form_typeNo(get, list) Form, default "10-K": "10-K" or "10-Q" for US filers, "20-F" or "40-F" for foreign issuers filing with the SEC. Korean, Japanese, Chinese and European filings use "10-K" for annual and "10-Q" for interim reports.
as_of_dateNo(get, list) Date "YYYY-MM-DD" (not in the future): only what had been filed by that day counts. Default: no cutoff.
role_labelNo(get) The statement or note name as the filer gave it, e.g. "CONSOLIDATED STATEMENTS OF OPERATIONS" or "Revenue Recognition"; a name that differs from the filing's is matched for 20 more credits. Give one of statement_type, role_label, block_index.
block_indexNo(get) The block's position as list returns it. Give one of statement_type, role_label, block_index.
fiscal_yearNo(get, list) Fiscal year of the filing (1990-2100).
statement_typeNo(get) "Income Statement", "Balance Sheet", "Cash Flow Statement", "Comprehensive Income" or "Stockholders Equity" (US filings only). Give one of statement_type, role_label, block_index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as_of_date
      Added value: +{
      +  "description": "(get, list) Date \"YYYY-MM-DD\" (not in the future): only what had been filed by that day counts. Default: no cutoff.",
      +  "format": "date",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses credit pricing per action (28, 48, 10), the surcharge for fuzzy role_label matching, that statement_type is US-only while role_label works in any filing, and the error behavior when a fiscal year has multiple filings ("the error then lists the quarters on file"). That is exactly the operational context annotations cannot carry.

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?

Front-loaded with the return-shape summary, then bulleted per-action guidance, then the filing-identification rule. Efficient overall, though the closing "Name the filing with filing_id, or with ticker and fiscal_year" restates what the schema already says.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with no output schema, the description supplies what the response contains for both actions (rows with value/period/unit/source; blocks with block_index/statement_type/role_label) and how to resolve a filing. Nothing an agent needs to call it correctly is missing.

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 the baseline is 3; the description still adds value by tying costs to parameter choices and reinforcing that the filing is named by filing_id or ticker+fiscal_year, not both. Much of the per-parameter wording overlaps the schema descriptions, so it is additive rather than transformative.

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 resource and scope: "Whole statements and notes of one filing, as filed: every row with its value, period, unit and source," then splits it into two named actions (get/list) with distinct return shapes. An agent can tell this apart from akkru_facts or akkru_filings without opening a schema.

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?

Explains the get vs list split and, for get, which of the three selectors to use and what each one accepts (statement_type for the five US main statements, role_label for any filer-named block, block_index for a position that list returns), which implies the list-then-get workflow. It does not name a sibling tool as an alternative, so the boundary with akkru_facts is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources