Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Get Filing (open any filing by accession — text, exhibit, section, passages)

get_filing
Read-onlyIdempotent

Open one SEC filing by accession number and read its text from Kaleidoscope's own filing store (never a sec.gov link). Use it whenever another tool hands you an accession (company_deals, company_red_flags, company_dilution, insider_liquidity, company_proxy_votes, ...).

With just accession: filing metadata (company, CIK, form, filing date), a table of contents — exhibits (type, title, size) and sections (10-K / 10-Q / 20-F / S-1 items) — and the first page of the main document's text. Then:

  • exhibit ('EX-10.1', '10.1', or the exhibit_seq) reads that exhibit — merger agreements, credit agreements, press releases (EX-99.1) usually live here;

  • section (item code '1A' / '7' / '2.02', or a name like 'Risk Factors' / 'MD&A') reads one item;

  • query returns up to 5 passages where a phrase occurs instead of a page, each with the offset to page from;

  • offset + max_chars (default 20,000, max 100,000) page through long text; follow next_offset until it is null.

Coverage: main documents 1994 onward, exhibits 1994 onward, sections for the forms sections has itemised (10-K / 10-Q / 20-F / S-1 family, 8-K items like '1.01' / '2.02', SEC comment letters). A filing missing here is a coverage gap, not proof it doesn't exist.

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": {
      "accession": "<accession>"
    },
    "name": "get_filing"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoYYYY-MM-DD. A filing is immutable; a filing dated after as_of returns not_filed_as_of.
queryNoReturn passages where this phrase occurs (in the chosen document / exhibit / section) instead of a page.
offsetNoCharacter offset to start the page at.
exhibitNoExhibit to read: 'EX-10.1', '10.1', '99.1', or its exhibit_seq.
sectionNoItem to read: '1A', 'Item 7', or a name ('Risk Factors', 'MD&A').
accessionYesSEC accession number, e.g. '0000773840-26-000084' (dashes optional).
max_charsNoPage size in characters (default 20000, max 100000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses where content comes from (internal store, not sec.gov), what a bare-accession call returns (metadata, TOC with exhibit types/titles/sizes, first page of text), pagination termination ('follow next_offset until it is null'), and coverage boundaries for documents, exhibits, and sections. The caveat that a missing filing is a coverage gap rather than proof of non-existence is a genuinely useful behavioral warning.

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?

Front-loaded one-sentence summary followed by a tight bullet list, one bullet per read mode, ending with a coverage note. No repetition of the schema and no filler; length is justified by the tool's four distinct modalities.

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 a 7-parameter, multi-mode tool with no output schema, the description supplies what an agent needs: what each mode returns, the shape of the default response, paging mechanics, and the historical coverage limits. Nothing essential to calling 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 3 is the baseline, but the description adds selection semantics: exhibit accepts 'EX-10.1', '10.1', or exhibit_seq; section accepts item codes or names like 'Risk Factors'/'MD&A'; query returns up to 5 passages with the offset to page from. It doesn't explain the as_of / not_filed_as_of behavior, leaving that entirely to the schema.

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 opening states a specific verb and resource — open one SEC filing by accession number and read its text — and immediately scopes the source ('Kaleidoscope's own filing store, never a sec.gov link'). The title plus the bullets make it distinguishable from sibling tools, which return derived data (deals, red flags, dilution) rather than raw filing text.

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?

Explicit routing guidance: 'Use it whenever another tool hands you an accession (company_deals, company_red_flags, company_dilution, insider_liquidity, company_proxy_votes, ...)'. It also explains which mode to choose for each need — exhibit for agreements/press releases, section for 10-K/8-K items, query for phrase lookup, offset+max_chars for paging.

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