Skip to main content
Glama

Mortgage lender profile (HMDA)

lender_lookup
Read-onlyIdempotent

A mortgage lender's own 2025 HMDA filing, by name or LEI: records, loans originated and their dollar total, the loan-type and loan-purpose mix, and its largest states. Not a rating; no per-lender approval or denial rate is given.

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": {
      "query": "<query>"
    },
    "name": "lender_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYespart of the lender's legal name, e.g. "Wells Fargo", or its 20-character LEI
stateNooptional: only lenders with HMDA records for property in this state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds substantive data-scope transparency: figures come from the lender's own 2025 filing and deliberately exclude approval/denial rates, which prevents misuse of the output. It says nothing about result size, matching behavior for partial names, or ambiguity when multiple lenders match.

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 tight sentences, front-loaded with the resource and lookup keys, followed by the exclusions. No filler. The phrase 'Not a rating' is slightly oblique in isolation but is immediately clarified by the clause that follows.

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

Completeness4/5

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

With only two fully documented parameters and no output schema, the description usefully enumerates the returned profile contents in place of a return schema, which is exactly what is needed here. The remaining gap is the unexplained state filter and no note on how multiple name matches are handled.

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 the schema already documents both parameters fully, including the 'part of legal name or 20-character LEI' example and the state pattern. The description echoes 'by name or LEI' but never explains the optional state filter (it only mentions 'largest states' as an output field), adding little beyond the schema. 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?

The description names the specific resource (a single mortgage lender's 2025 HMDA filing), the two lookup keys (name or LEI), and the contents of the profile (records, originations and dollar totals, loan-type/purpose mix, top states). That is far more than a restatement of the name. It does not explicitly contrast itself with the county-level sibling (county_lending_market), so it falls short of a 5.

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

Usage Guidelines4/5

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

It gives a clear selection cue ('by name or LEI') and an explicit negative boundary: 'Not a rating; no per-lender approval or denial rate is given,' which steers an agent away from using this for approval/denial analysis. It stops short of naming an alternative tool for that need, so it is not a 5.

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