mtgmon Mortgage Analytics

Dataset status

get_dataset_status

Read-onlyIdempotent

Coverage, freshness, and build metadata for every mtgmon dataset. No arguments.

Use for: "how current is the data", finding the latest available month or HMDA year before quoting figures, or diagnosing another tool's meta.available=false.

Returns data.datasets, a list of {name, description, category, provider, coverage, last_updated, last_updated_label, stats, refresh} covering GSE loan performance, HMDA, market rates, SEC filings, and derived marts; and data.build {app, lake, cache_backend, cache}. Refresh cadences differ by dataset; read each row's coverage and last_updated.

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": "get_dataset_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

addedOutput schema / $defs / ResultMeta / properties / cache_status / description

Added value: +"Server cache state: hit; stale (older than its TTL, still served); stale-refresh; miss (warming, retry after a few seconds); failed or required-miss (not available now, a retry soon will not help); none; unknown."

First observedJul 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world, yet the description still adds substantive context: no auth or API key, no PII, the public endpoint's rate limits (about 60 req/min, 250 tool calls/day per client IP), and the {data, meta} result envelope with its meta fields. The only deduction is that 'read-only ... idempotent and safe to retry' partly restates the annotations, though the retry caveat attached to cache_status is genuinely new information.

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?

It is front-loaded with purpose, then a labelled 'Use for:', then returns, then behavior, then result shape and failure handling, which is easy to scan. It is on the long side for a no-argument status call, and the sentence listing safety traits duplicates the annotation block rather than earning its space.

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 zero-parameter tool with an output schema, the definition still documents the dataset categories covered (GSE loan performance, HMDA, market rates, SEC filings, derived marts), warns that refresh cadences vary, and explains the failure mode when meta.available is false. Nothing an agent needs in order to call it or interpret its result 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?

There are zero parameters, so the baseline is 4; the description correctly states 'No arguments,' which matches the empty schema. There is no additional parameter meaning to convey, so nothing pushes it above the baseline.

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 opening sentence names the exact resource and the three things it reports on (coverage, freshness, build metadata) and adds 'No arguments,' which immediately scopes the call. None of the listed siblings (get_loan_performance, get_market_snapshot, etc.) serve this metadata role, so the agent can distinguish it without opening a 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 gives explicit scenarios ('how current is the data', finding the latest available month or HMDA year before quoting figures, diagnosing another tool's meta.available=false) rather than vague encouragement. It also states the remedy path when meta.available is false, including the retry condition tied to cache_status 'miss', which is when-to-use guidance at a very fine grain.

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?