Skip to main content
Glama
Sign In

Dominick Prevete: DSCR Lender Data

by com.dominickprevete
OverviewDiscussionsAdmin

Rate ranges

rate_ranges
Read-onlyIdempotent

Indicative starting rate by program, from the site's single rate source, stamped with its as-of month (currently November 2026). These are the published ranges, not pricing on any deal.

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

Input Schema

NameRequiredDescriptionDefault
programNoProgram key to filter to; omit for all. One of: dscr, dscr_cash_out, short_term_rental, fix_and_flip, ground_up, rental_portfolio, bridge, commercial

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"Program to filter to: dscr, str, fixAndFlip, groundUp, portfolio, commercial, bridge"New value: +"Program key to filter to; omit for all. One of: dscr, dscr_cash_out, short_term_rental, fix_and_flip, ground_up, rental_portfolio, bridge, commercial"
    • addedInput schema / properties / program / enum
      Added value: +[
+  "dscr",
+  "dscr_cash_out",
+  "short_term_rental",
+  "fix_and_flip",
+  "ground_up",
+  "rental_portfolio",
+  "bridge",
+  "commercial"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely useful context: a single authoritative source, as-of month stamping with the current value (November 2026), and the fact that values are indicative rather than deal pricing. It stops short of describing response structure or refresh cadence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences with zero filler; the core meaning is front-loaded and the qualifier about deal pricing is placed after the substance where it belongs.

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 one optional parameter, full enum documentation, and no output schema, the description supplies the essential context an agent needs: what the numbers represent, their source, and their freshness. Only the shape of the returned ranges is left unstated, which is minor for this simple lookup.

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 enum parameter is fully enumerated with an 'omit for all' default. The description adds only the phrase 'by program', which restates what the schema already documents, so 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?

States a specific resource (indicative starting rate ranges) and scope (by program, from the single rate source) in a single clear clause. It does not name or contrast with any sibling such as loan_programs or investor_lenders_aggregate, 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?

The closing caveat ('published ranges, not pricing on any deal') implicitly scopes when the tool is appropriate, but there is no explicit when-to-use guidance and no alternative tool is named for deal-level pricing or program details.

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

All Dominick Prevete: DSCR Lender Data toolsInspect
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