beatandraise.com SEC Filings

Search Within a Filing

search_document

Read-onlyIdempotent

Search within a filing's documents for specific terms. Returns matching lines with context.

If filename is omitted, searches every readable document in the filing (the main document and its exhibits, e.g. an 8-K's press release AND its CFO commentary), up to 12 files. A filing with only XML forms (Form 144, 3/4/5, 13F, N-PORT, D) is searched as raw XML lines, so element names (aggregateMarketValue, netAssets) match as well as values. If filename is provided, searches only that file. Each file in the result carries its own source (beatandraise_url) — cite the file the match came from.

Workflow:

Use get_filings to find the accession number for the filing you want
Call this tool with just accession_number and query — it will search all its documents
Optionally use get_filing_detail to see all files, then search a specific one by filename

Supports multiple search terms separated by commas — lines matching any term are returned. A comma inside a number is kept: "3,007" or "464,391" is searched as one figure.

Args: accession_number: SEC accession number (e.g. "0001045810-25-000023") query: Search terms, comma-separated (e.g. "singapore,revenue" or "risk factors") cik: Optional. CIK of the filer (e.g. "0000320193"); found from the accession number when left out filename: Optional document filename. If omitted, searches all readable documents. context_lines: Lines of context around each match (0-50, default 10)

Input Schema

Name	Required	Description	Default
`cik`	No
`query`	Yes
`filename`	No
`context_lines`	No
`accession_number`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/destructive=false, yet the description adds real behavioral context: a 12-file cap on the all-documents search, raw-XML handling for XML-only forms, and the per-file source URL for citation. It does not discuss truncation behavior when many lines match, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and return shape, then scope behavior, then a numbered workflow. The trailing 'Args:' block largely restates the schema, which is mild redundancy rather than noise, but it slightly bloats an otherwise tight description.

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 5-parameter tool with an output schema, everything an agent needs to call it correctly is present: required vs optional, fallback derivation of cik, scope of the search, result shape, and citation guidance. Return-value detail is appropriately deferred to the output schema.

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%, so the description must carry the burden and it does: it explains accession_number format, comma-separated query semantics (including the comma-in-number rule), that cik is derived when omitted, filename's all-vs-one behavior, and context_lines' 0-50 range with default 10.

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 ('Search within a filing's documents') plus the return shape ('matching lines with context'). It is clearly distinguished from siblings like get_document (retrieval) and search_filings (filing-level discovery) via the workflow section.

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?

Provides an explicit three-step workflow naming get_filings and get_filing_detail, plus the key selection rule: omit filename to search all documents, include it to search one. Exclusions and ordering are spelled out rather than inferred.

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

All beatandraise.com SEC Filings tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?