Skip to main content
Glama

mtgmon Mortgage Analytics

by io.github.lorenzopi
OverviewDiscussionsAdmin

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 the data is unavailable or the cache is still warming (retry after a few seconds); never report it as zero.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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."
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: no auth or API key, no PII, per-IP rate limits (~60 req/min, 250 calls/day), and the important gotcha that only filings whose summary finished are listed, that summaries are machine-generated and should be checked against edgar_url, and that meta.available=false means unavailable/warming rather than zero.

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?

Structured as scope → Use for → Do not use for → Returns → Behavior, with the routing information front-loaded. Despite its length, every sentence carries distinct, actionable information (rate limits, summary caveat, pagination, meta.available semantics) with no filler.

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 search tool with an output schema and full annotations, this covers the remaining gaps an agent needs: when the data is unavailable, how pagination terminates, the trust level of machine summaries, and where to go for full text. Nothing material is missing.

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 baseline is 3, and the description adds value the schema does not: the default sort order, the meaning of cursor chaining via data.next_cursor, and the at-most-limit row semantics. It does not add per-parameter syntax beyond the schema, so it stops short of a 5.

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?

Opens with a specific verb (Search) plus resource (SEC EDGAR filings) and narrows scope to mortgage-related public companies that mtgmon has summarized, with a stated sort order (newest filing date first). It is clearly distinguishable from the sibling get_sec_filing, which it positions as the follow-up call.

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?

Explicit 'Use for' (finding 10-K/10-Q/8-K by ticker, CIK, form, keyword, or date window) and 'Do not use for' (full filing text, non-mortgage companies) sections, plus a named alternative — get_sec_filing — for retrieving the record once filing_id is known. Nothing is left to inference.

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

All mtgmon Mortgage Analytics toolsInspect
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