Skip to main content
Glama

get_filing_text

Retrieve the full text of SEC filings for any ticker to read the company's actual statements behind the numbers. Use when financial metrics need context from the original filing.

Instructions

The text of a filing as filed, markup stripped, in windows.

Use this when the numbers raise a question they cannot answer — a margin
that moved, a quarter that beat and sold off anyway, a net income figure
that outran operating income. `get_filings` gives you the date; this gives
you what the company actually said.

Large filings are returned in windows. `truncated` and `next_offset` tell
you whether there is more; a silently cut filing reads like a complete one.
Prefer `search_filing_text` when you know what you are looking for.

Args:
    ticker: Stock symbol.
    accession: Specific filing accession number. Takes precedence.
    form: Read the newest filing of this form instead, e.g. "10-Q".
    offset: Character offset to start from, for paging.
    max_chars: Characters to return, capped at 100,000.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formNo
offsetNo
tickerYes
accessionNo
max_charsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description carries the full burden and excels. It discloses key behaviors: markup stripping, pagination via windows, truncation signaling through `truncated` and `next_offset`, and the hierarchy of `accession` over `form`. Also notes the `max_chars` cap of 100,000, preventing silent data loss.

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 well-structured, starting with a one-sentence summary, followed by usage context, important pagination behavior, and an Args list. Every sentence adds value—no fluff or redundancy.

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?

Despite having an output schema (not shown), the description still provides essential context: purpose, usage scenarios, pagination mechanics, and parameter semantics. It covers all aspects an agent needs to correctly select and invoke the tool, making it complete for practical use.

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 coverage is 0%, but the description fully compensates. Each parameter is explained with its role, including special behaviors: `accession` takes precedence, `form` selects newest filing of that form, `offset` for paging, and `max_chars` with an explicit cap. This adds significant meaning beyond the raw 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 first sentence clearly states what the tool does: retrieves filing text as filed, with markup stripped, in windows. It distinguishes itself from siblings by noting that `get_filings` provides dates while this tool provides the actual text, and `search_filing_text` is for targeted searches.

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?

Explicitly states when to use the tool: 'Use this when the numbers raise a question they cannot answer' with concrete examples. It also gives an alternative: 'Prefer `search_filing_text` when you know what you are looking for.' This provides clear decision rules for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Saivikaskillamsetty/tradingdesk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server