Skip to main content
Glama

OCC Mortgage Servicing Performance

mortgage_performance
Read-only

Delinquency, foreclosure and risk-category counts for mortgages serviced by seven large national banks. (Source: OCC Mortgage Metrics Report.)

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

Input Schema

NameRequiredDescriptionDefault
periodNoLatest quarter shown, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful scope context (seven large national banks, OCC source), but does not state default behavior when period is omitted or what the response contains. Given annotation coverage, this partial disclosure is adequate but not rich.

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?

Two short sentences with the scope statement front-loaded and the source in parentheses. Efficient, though it omits any leading action verb, which slightly weakens the framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only data retrieval tool with one optional parameter, the description explains the data domain but is silent on default period behavior and the shape of returned measures. There is no output schema, so more detail on the returned breakdown would have helped.

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 single optional period parameter is documented in the schema with a format example. The description adds no meaning about the parameter, so the baseline of 3 applies rather than a higher score.

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 names a concrete resource and metric set: delinquency, foreclosure, and risk-category counts for mortgages serviced by seven large national banks, with the OCC Mortgage Metrics Report as source. An agent can tell this is mortgage servicing performance data, though there is no verb and no explicit distinction from data-oriented siblings such as credit_quality or nonbank_mortgage_states.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool, when to prefer an alternative (e.g., nonbank mortgage coverage), or what the period parameter does when omitted. The agent must infer usage entirely from the one-line data summary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources