Skip to main content
Glama

Dominick Prevete: DSCR Lender Data

Investor lenders by state

investor_lenders_by_state
Read-onlyIdempotent

Top investment-property lenders in any one of the 50 states and DC, from 2025 HMDA loan-level data: lender name, LEI, loan count, volume, average loan and purchase share, plus state totals and the retrieval date. Read-only; figures are the filing record, not a recommendation.

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": {
      "state": "<state>"
    },
    "name": "investor_lenders_by_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, 1–50 (default 25)
stateYesTwo-letter state code, one of NJ, FL, PA, NY, TX, GA, NC, TN, OH, AZ, CA, CO, VA, MD, CT, IL, MO, MI, IN, OK, WA, AL, MA, SC, MS, NM, WI, LA, AR, KY, MN, OR, KS, IA, UT, NH, ID, WV, ME, MT, HI, RI, NE, DE, ND, NV, SD, WY, AK, VT, DC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code, one of NJ, FL, PA, NY, TX, GA, NC, TN, OH, AZ, CA, CO, VA, MD, CT, IL, MO, MI, IN, OK, WA, AL, MA, SC, MS, NM"New value: +"Two-letter state code, one of NJ, FL, PA, NY, TX, GA, NC, TN, OH, AZ, CA, CO, VA, MD, CT, IL, MO, MI, IN, OK, WA, AL, MA, SC, MS, NM, WI, LA, AR, KY, MN, OR, KS, IA, UT, NH, ID, WV, ME, MT, HI, RI, NE, DE, ND, NV, SD, WY, AK, VT, DC"
  2. Changed1 schema field changed
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code, one of NJ, FL, PA, NY, TX, GA, NC, TN, OH, AZ, CA, CO, VA, MD, CT"New value: +"Two-letter state code, one of NJ, FL, PA, NY, TX, GA, NC, TN, OH, AZ, CA, CO, VA, MD, CT, IL, MO, MI, IN, OK, WA, AL, MA, SC, MS, NM"
  3. Changed3 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +25
    • changedInput schema / properties / limit / maximum
      Previous value: -9007199254740991New value: +50
    • changedInput schema / properties / limit / minimum
      Previous value: --9007199254740991New value: +1
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: data provenance (2025 HMDA loan-level filing record), which fields are returned, and that state totals plus a retrieval date are included. It stops short of describing ranking behavior or how the limit interacts with totals.

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?

One dense sentence delivers scope, source, and returned fields, followed by a short caveat sentence. Everything earns its place and the scope is front-loaded, though the field enumeration is somewhat list-heavy for a definition whose schema could imply the shape.

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?

No output schema exists, so the description rightly names the returned fields, the data vintage, and the retrieval date. However, it never states what 'top' is ranked by (loan count vs volume), which is the single most decision-relevant fact for interpreting the output, and it omits any note on how limit truncates the ranking.

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%: state carries an explicit enumeration of valid two-letter codes and limit documents the 1–50 range with a default of 25. The description adds nothing parameter-specific (it doesn't even reference the limit), so baseline 3 is appropriate when the schema does all the work.

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?

States a specific resource and scope: 'Top investment-property lenders in any one of the 50 states and DC' from 2025 HMDA data, and enumerates what comes back (lender name, LEI, loan count, volume, average loan, purchase share). An agent knows exactly what it retrieves, though the sibling investor_lenders_aggregate is never named or contrasted, so differentiation is left to inference.

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?

Usage is implied by the scope ('any one of the 50 states and DC'), which tells the agent this is a single-state lookup, but there is no explicit when-to-use, no prerequisite, and no routing to investor_lenders_aggregate for the multi-state case. The read-only disclaimer is the only guidance-adjacent statement.

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