Skip to main content
Glama

OptimistFi

get_filing_text

Read-only

Text of an issuer's filing of a given form — the most recent, or a HISTORICAL one.

period: select an older filing instead of the latest — a fiscal year ("2021") or a period-end
date ("2023-06-30", the quarter/year the filing covers). Omit for the most recent. This is how you
read a specific year's 10-K or a specific quarter's 10-Q, not just today's.
section: business · risk_factors · legal_proceedings · mdna · financial_statements. STRONGLY
prefer a section — a full 10-K is ~55,000 tokens and will swamp your context.
find: jump straight to a keyword ("restructuring", "Value-at-Risk", "pension", a segment name)
instead of reading from the top — returns the window around the first match and reports
data.match_count. This is how you pull ONE number out of a 400k-char filing in a single call;
combine with section, or use it alone when a section isn't detected. To reach a later match, call
again with offset = data.window_start + data.chars_returned.
offset: start position in the (section or full) body, for paging a long section.
Output is always bounded and sets data.truncated when there is more after this window, with
chars_total showing the full length and data.window_start where this window began.
For an earnings press release / adjusted (non-GAAP) figures, use get_filings(kind="press_releases"),
which serves the EX-99 exhibit text — those numbers are not in the 10-K/10-Q body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
findNo
formNo10-K
entityYes
offsetNo
periodNo
sectionNo
max_charsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses bounded output, the data.truncated flag, chars_total, window_start, match_count, and how offset paging works. It also warns about the ~55,000-token cost of a full 10-K, which is valuable behavioral context.

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?

The description is dense but every sentence earns its place: purpose, parameter semantics, output behavior, and sibling routing are all covered without fluff. It is front-loaded with the core purpose and scoping distinction.

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 tool with 1 required parameter, an output schema, and a readOnly annotation, the description covers all operational concerns: historical selection, section guidance, keyword jumping, paging, bounded output, and the key alternative tool. Nothing critical is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries full responsibility for parameter meaning. It thoroughly explains period, section, find, offset, and output bounds, with concrete examples for fiscal year, period-end date, keyword search, and paging 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: retrieving the text of an issuer's filing for a given form, with an explicit historical vs. most-recent distinction. It also differentiates itself from get_filings by routing press-release/EX-99 content to that sibling.

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?

It gives concrete when-to-use guidance for period, section, find, and offset, including when to prefer get_filings(kind='press_releases') for non-GAAP figures. The instruction to STRONGLY prefer a section because of token size is an explicit usage guideline.

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