mtgmon Mortgage Analytics

SEC filing detail

get_sec_filing

Read-onlyIdempotent

Full detail for one SEC filing: metadata and EDGAR link, mtgmon's machine-generated summary, which tracked mortgage entities the filing concerns and in what role, named people with titles and compensation, extracted financial facts, and ownership rows.

Get the filing_id from search_sec_filings first.

Returns data.filing {filing_id, accession_number, filer_cik, form, filing_date, company_name, description, canonical_summary, summary_status, summary_model, edgar_url, ...}, data.associations [{display_name, ticker, cik, relationship_role, summary, link_status, ...}], data.people [{name, title, compensation, note}], data.financials [{metric, value, unit, period}], and data.ownership. Each list is capped. Verify summaries against the linked filing before relying on them.

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

Name	Required	Description	Default
`filing_id`	Yes	Filing identifier exactly as returned in a search_sec_filings result's filing_id field, typically the SEC accession number such as '0002100121-26-001023'. Letters, digits, '-' and '_' only.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

addedInput schema / properties / filing_id / description

Added value: +"Filing identifier exactly as returned in a search_sec_filings result's filing_id field, typically the SEC accession number such as '0002100121-26-001023'. Letters, digits, '-' and '_' only."

AddedAug 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description goes beyond the readOnlyHint and idempotentHint annotations by stating 'read-only, no auth or API key, no PII, idempotent and safe to retry.' It discloses rate limits (60 req/min, 250 calls/day) and explains the meta.available flag behavior, including that a false value means the cache is warming and to retry rather than reporting 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?

The description is structured with a clear purpose sentence, a prerequisite instruction, a detailed return shape, and a behavior section. Every sentence adds operational information; no filler. The most critical usage guidance (obtain ID from search_sec_filings) is front-loaded.

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?

The description fully equips an agent to call the tool: it specifies the return structure with field examples, explains the meta wrapper and its fields, addresses error conditions (meta.available false), and notes list caps. Combined with the output schema, nothing necessary 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?

The schema already provides 100% coverage for filing_id, including format and examples. The description adds value by telling the agent to obtain the ID from search_sec_filings, ensuring correct source. Since the schema is exhaustive, the description's contribution is supplementary but useful.

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?

The description opens with 'Full detail for one SEC filing' and enumerates the exact content areas (metadata, EDGAR link, machine-generated summary, associations, people, financials, ownership). It clearly distinguishes itself from search_sec_filings and other analytics siblings by focusing on a single filing's detailed data.

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?

It explicitly instructs 'Get the filing_id from search_sec_filings first,' establishing the prerequisite workflow and when to use this tool. It also advises to 'Verify summaries against the linked filing before relying on them,' adding a caution about usage context.

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 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?