mtgmon Mortgage Analytics

SEC profile identity

get_sec_profile

Read-onlyIdempotent

Return a firm's, person's or facility's identity and record counts. Use list_sec_records for all records.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "get_sec_profile"
  }
}

Input Schema

Name	Required	Description	Default
`profile_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.6/5.0

Behavior5/5

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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive, but the description adds material context they cannot express: no auth or API key, no PII, and concrete rate limits (~60 req/min, 250 calls/day per client IP). Most importantly it discloses the response envelope and the semantic rule that meta.available=false must never be reported as zero.

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?

Purpose and the sibling boundary are front-loaded, then behavior, rate limits, and the failure-mode rule follow in a sensible order. It is slightly dense -- the enumerated list of meta fields is verbose -- but nearly every clause carries operational value.

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?

Although an output schema exists, the description goes further by explaining the {data, meta} envelope and the meaning of the availability flag, which is the main way an agent could misuse this tool. For a single-parameter read tool with rich annotations, nothing needed 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% and the sole parameter already carries a pattern and a description pointing at SEC profile/record search as its source. The prose adds no further meaning about profile_id format or origin, so the baseline 3 applies.

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 a specific verb and resource: 'Return a firm's, person's or facility's identity and record counts.' It also names the scope boundary against the sibling list_sec_records, so an agent can distinguish the two tools without opening either schema.

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 routes bulk record retrieval to list_sec_records while reserving this tool for identity and counts. It also supplies conditional operating guidance -- retry only when meta.cache_status is 'miss', otherwise report unavailable -- which is decision logic an agent can act on directly.

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?