Skip to main content
Glama

StockPortfolio.pro

Get SEC filing content

get_filing
Read-only

Read one SEC filing — its metadata plus short excerpts of its text. Identify it by accession number (preferred, as returned by search_filings), or by ticker with an optional filing type, which defaults to the company’s latest 10-K. Request a named section such as "Risk Factors", "MD&A" or "Legal Proceedings", or search the filing for a term. Returns excerpts with their section and the filing URL, not the whole document. Use get_company_fundamentals for reported numbers.

Input Schema

NameRequiredDescriptionDefault
queryNoOptional term to find inside the filing; excerpts around each match are returned.
tickerNoUS ticker. Required when accession_number is not given, optional otherwise.
sectionNoOptional section name, e.g. "Risk Factors", "MD&A", "Business", "Legal Proceedings".
max_charsNoMaximum characters per excerpt or section.
filing_typeNoOptional filing type when no accession number is given, e.g. 10-K, 10-Q or 8-K. Defaults to the latest 10-K.
max_excerptsNo
accession_numberNoSEC accession number, e.g. 0000320193-25-000079. Enough on its own — the company is derived from it.

Output Schema

NameRequiredDescriptionDefault
filingNo
companyNo
sectionNo
excerptsNo
match_countNo
available_sectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description still adds meaningful behavior beyond that: output is excerpts with section labels and the filing URL rather than the whole document, and the ticker path silently defaults to the latest 10-K. It does not mention any rate limits, auth needs, or what happens when a section name is unrecognized.

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?

Three dense sentences, front-loaded with what the tool returns and how to identify the filing, then the modes, then the disambiguation pointer. Every clause carries information and nothing is repeated from the schema.

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?

An output schema exists, so return values need not be detailed, yet the description still notes that only excerpts plus URL come back. Combined with the identification precedence rules and the sibling routing, an agent has everything needed to invoke this correctly.

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 86%, so the schema already documents most parameters; baseline would be 3. The description goes further by explaining the precedence between accession_number and ticker, the default filing_type, and by giving concrete section examples ("Risk Factors", "MD&A", "Legal Proceedings") that clarify the otherwise free-form section parameter.

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 verb and resource ("Read one SEC filing — its metadata plus short excerpts of its text") and immediately scopes what is returned versus the full document. It also explicitly distinguishes itself from siblings by naming search_filings as the source of accession numbers and get_company_fundamentals as the tool for reported numbers.

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?

Gives explicit routing: prefer accession_number, fall back to ticker plus optional filing_type which defaults to the latest 10-K, and use get_company_fundamentals for reported numbers. It also explains the two retrieval modes (named section vs. term search), leaving little 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