mtgmon Mortgage Analytics

Search SEC profiles

search_sec_profiles

Read-onlyIdempotent

Return resolved firms, people or facilities. Continue with data.next_cursor; names alone are not identity proof.

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_profiles"
  }
}

Input Schema

Name	Required	Description
`q`	No	Name search; empty means all resolved profiles.
`cik`	No	Exact SEC CIK; empty disables this filter.
`lei`	No	Exact Legal Entity Identifier; empty disables this filter.
`kind`	No	Profile or record kind; empty means all kinds.
`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.

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?

Beyond the annotations (readOnly, idempotent, non-destructive, open world), it discloses that no auth or API key is required, states concrete rate limits (~60 req/min, 250 calls/day per client IP), and describes the {data, meta} envelope with its meta fields. Most valuably, it explains the failure mode: when meta.available is false, do not report zero, and retry only when meta.cache_status is 'miss'.

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?

The purpose is front-loaded in the first sentence, followed by behavior, limits, and result handling in a logical order, with no filler. It is dense and slightly long, but each sentence carries operational information an agent would otherwise lack.

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 6-parameter, open-world search with an output schema, the description covers what is needed to call and interpret it: no auth, rate limits, pagination via next_cursor, the meta envelope, and the critical unavailable-vs-zero distinction. Duplication with the output schema is limited to field naming, which is acceptable.

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 coverage is 100%, so all six parameters (q, cik, lei, kind, limit, cursor) are already documented in the schema, and the baseline applies. The description reinforces cursor continuation semantics with 'Continue with data.next_cursor' but adds no per-parameter meaning beyond what the schema states.

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?

The description states a specific resource ('resolved firms, people or facilities') returned by a search, so an agent can tell it is a profile-search tool. However, it never names or distinguishes itself from siblings such as search_sec_filings, list_sec_records, or get_sec_profile, so the differentiation has to be inferred from the tool name.

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?

'Continue with data.next_cursor; names alone are not identity proof' gives real operational guidance for pagination and for not over-trusting name matches. But there is no explicit when-to-use/when-not guidance relative to search_sec_filings, get_sec_profile, or list_sec_records, so the choice among them 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 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?