Skip to main content
Glama

mtgmon Mortgage Analytics

Search SEC filings

search_sec_filings
Read-onlyIdempotent

Search SEC EDGAR filings of mortgage-related public companies (lenders, servicers, mortgage REITs, insurers, GSEs) that mtgmon has summarized. Newest filing date first.

Use for: finding a company's 10-K, 10-Q, 8-K, or other filings by ticker, CIK, form type, keyword, or date window, and getting the filing_id to pass to get_sec_filing. Do not use for: full filing text (only summaries are stored) or companies outside the mortgage sector.

Returns data.filings (at most limit rows of {filing_id, accession_number, filer_cik, form, filing_date, company_name, description, summary_status, summary_excerpt, summary_created_at, edgar_url}) and data.next_cursor (pass back as cursor for the next page; null when exhausted; meta.truncated is true when more pages exist). Only filings whose summary processing finished are listed; summaries are machine-generated and should be checked against edgar_url.

Behavior: read-only, no auth or API key, no PII, idempotent and safe to retry. The public endpoint https://mtgmon.com/mcp allows about 60 requests/min and 250 tool calls/day per client IP. Result shape is {data, meta}; meta carries available, as_of, source_scope, weighting, units, cache_status, caveats, and truncated. If meta.available is false, never report it as zero: retry after a few seconds only when meta.cache_status is 'miss' (warming); otherwise report the data as unavailable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_sec_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key of the filer, digits only, e.g. '1805284'. Empty (default) = any filer.
formNoSEC form type, e.g. '10-K', '10-Q', '8-K', 'S-1', 'DEF 14A'. Case-insensitive. Empty (default) = all forms.
limitNoMaximum filings per page, 1-25 (default 10).
queryNoFree-text keyword search over company name and summary text, e.g. 'servicing portfolio sale'. Empty (default) = no text filter.
cursorNoOpaque pagination token copied from a previous result's data.next_cursor. Empty (default) = first page.
tickerNoStock ticker of the filer, e.g. 'RKT', 'UWMC', 'PFSI'. Case-insensitive; retired symbols such as 'GHIV' also match. Empty (default) = any.
to_dateNoLatest filing date, ISO YYYY-MM-DD; must not be before from_date. Default: no upper bound.
from_dateNoEarliest filing date, ISO YYYY-MM-DD. Default: no lower bound.
summary_statusNo'' (default: all), 'summarized' (a machine summary exists), or 'unavailable' (summary could not be produced).

Output Schema

NameRequiredDescriptionDefault
dataNo
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / $defs / ResultMeta / properties / cache_status / description
      Added value: +"Server cache state: hit; stale (older than its TTL, still served); stale-refresh; miss (warming, retry after a few seconds); failed or required-miss (not available now, a retry soon will not help); none; unknown."
  2. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker of the filer, e.g. 'RKT', 'UWMC', 'PFSI'. Case-insensitive. Empty (default) = any."New value: +"Stock ticker of the filer, e.g. 'RKT', 'UWMC', 'PFSI'. Case-insensitive; retired symbols such as 'GHIV' also match. Empty (default) = any."
  3. Changed9 schema fields changed
    • addedInput schema / properties / cik / description
      Added value: +"SEC Central Index Key of the filer, digits only, e.g. '1805284'. Empty (default) = any filer."
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque pagination token copied from a previous result's data.next_cursor. Empty (default) = first page."
    • addedInput schema / properties / form / description
      Added value: +"SEC form type, e.g. '10-K', '10-Q', '8-K', 'S-1', 'DEF 14A'. Case-insensitive. Empty (default) = all forms."
    • addedInput schema / properties / from_date / description
      Added value: +"Earliest filing date, ISO YYYY-MM-DD. Default: no lower bound."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum filings per page, 1-25 (default 10)."
    • addedInput schema / properties / query / description
      Added value: +"Free-text keyword search over company name and summary text, e.g. 'servicing portfolio sale'. Empty (default) = no text filter."
    • addedInput schema / properties / summary_status / description
      Added value: +"'' (default: all), 'summarized' (a machine summary exists), or 'unavailable' (summary could not be produced)."
    • addedInput schema / properties / ticker / description
      Added value: +"Stock ticker of the filer, e.g. 'RKT', 'UWMC', 'PFSI'. Case-insensitive. Empty (default) = any."
    • addedInput schema / properties / to_date / description
      Added value: +"Latest filing date, ISO YYYY-MM-DD; must not be before from_date. Default: no upper bound."
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: no auth/API key, no PII, ~60 req/min and 250 calls/day per client IP, opaque cursor pagination with meta.truncated, and an explicit recovery protocol for meta.available=false that warns against reporting zero. It also discloses that only summary-completed filings are listed and that summaries are machine-generated and should be verified against edgar_url.

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, then use/do-not-use, return shape, and behavior — each block is scannable and every sentence carries information. The field-by-field enumeration of data.filings is partly redundant with the existing output schema, though the cursor/truncated semantics and the unavailability protocol justify most of that paragraph.

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 9-parameter, zero-required search tool with annotations and an output schema, the description covers purpose, exclusions, pagination, rate limits, and degraded-response handling. An agent could invoke and recover from this tool correctly without opening any other reference.

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 100%, so the per-parameter baseline is 3; the description adds value by disclosing result ordering and the summary-completion filter that shapes what any combination of filters can return. There is a mild ambiguity between 'only filings whose summary processing finished are listed' and the summary_status enum's 'unavailable' value, which the description does not reconcile.

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 SEC EDGAR filings'), narrows the corpus to mortgage-related public companies that mtgmon has summarized, and specifies default ordering ('Newest filing date first'). It also distinguishes itself from the sibling get_sec_filing by naming the handoff role of the returned filing_id.

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?

Uses explicit 'Use for:' and 'Do not use for:' clauses, naming the accepted lookup dimensions (ticker, CIK, form type, keyword, date window) and the two exclusions (full filing text, non-mortgage-sector companies). It further directs the agent to get_sec_filing for the filing body, so the alternative is named rather than inferred.

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