Get the full detail of a single SEC filing by ticker and accession number (the unique SEC filing ID, e.g. '0000320193-26-000011').
Use this after get_filings or get_guidance has identified a specific
filing you want to inspect in full.
| Name | Required | Description | Default |
|---|---|---|---|
| ticker | Yes | ||
| accession_number | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of disclosing behavioral traits. It only states that it gets 'full detail' without describing what that entails (e.g., response format, size, pagination, rate limits, or permissions). The description adds no safety or side-effect context beyond the implied read-only nature of 'get.'
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no redundancy. The first sentence leads with the core function and primary parameter, and the second provides workflow guidance. Every word contributes to understanding the tool's purpose and usage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given there is no output schema, the description should hint at the return value. 'Full detail' is vague and could mean anything from metadata to the entire filing text. While the usage guidance is helpful, the lack of return structure or additional behavioral context makes the description incomplete for a tool with no output schema or annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate. It explains the accession number with an example and context ('unique SEC filing ID'), which adds meaning. However, the ticker parameter is only mentioned by name without any format or clarification. The description partially bridges the schema gap but leaves one parameter semantically thin.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves the full detail of a single SEC filing using ticker and accession number. It explicitly names the resource (SEC filing) and the unique identifier format, distinguishing it from sibling tools like get_filings which list filings. The verb 'get' and the scope 'single filing' make the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit usage guidance: 'Use this after get_filings or get_guidance has identified a specific filing you want to inspect in full.' This defines when to use the tool relative to alternatives, naming the predecessor tools and clarifying the workflow. It avoids ambiguity about when this tool should be invoked.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of SEC filings (company info, filings list, detail, guidance, sector, signals, transcripts, search, earnings calendar, sector listing). No two tools have overlapping purposes.
Most tools follow a 'get_<noun>' pattern (e.g., get_filings, get_guidance), but list_sectors and search_filings deviate. The naming is still clear and intuitive.
10 tools is well-scoped for a filing API—covers all major retrieval needs without redundancy or excess.
The tool surface covers the full lifecycle of filing retrieval: discovery (search, sector, calendar), listing, detail, and specialized extraction (guidance, signals, transcripts). No obvious gaps for the domain.