mtgmon Mortgage Analytics

SEC source evidence

get_sec_record_evidence

Read-onlyIdempotent

Return a page of exact source quotes, document URLs and source locations for a record.

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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "record_id": "<record_id>"
    },
    "name": "get_sec_record_evidence"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum records per page, 1–100. All records remain accessible through next_cursor.
`cursor`	No	Opaque next_cursor from the previous page of this exact query.
`record_id`	Yes	Stable identifier returned by SEC profile or record search.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds substantially more: no auth or API key, no PII, concrete rate limits (~60 req/min, 250 calls/day per IP), the {data, meta} envelope, and the critical warning not to report meta.available=false as zero. That last point is exactly the kind of behavioral trap an agent would otherwise fall into.

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 the return payload, then behavior, then the failure-mode rule — a sensible priority order with no filler. The enumeration of meta keys is slightly list-heavy, but each name is actionable for interpreting results.

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?

Despite an output schema existing, the description still explains the meta semantics (available, cache_status, truncated) that an agent needs to avoid misreporting results. Combined with rate limits and retry policy, nothing material for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% — limit, cursor and record_id are each documented with ranges and provenance in the schema itself. The description adds no syntax, format or edge-case meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Return a page of exact source quotes, document URLs and source locations for a record" gives a concrete verb plus the exact payload the agent gets back, which clearly separates it from profile/search siblings. It stops short of naming an alternative tool, so sibling differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (fetch evidence for a given record_id) and adds a real decision rule for the unavailable case: retry only when meta.cache_status is 'miss', otherwise report unavailable. It never says when to prefer get_sec_filing or search_sec_filings over this tool, so the when-not guidance is limited to error handling rather than tool selection.

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?