Dominick Prevete: Instant Term Sheet

Request an Instant Term Sheet

request_instant_term_sheet

Request a written term sheet for a business-purpose loan on a non-owner-occupied 1–4 unit investment property, emailed to the investor with a private download link. Instant where the deal fits the programs; otherwise an answer within 24 hours. A term sheet is indicative and not a commitment to lend. Every request, purchase or refinance, needs the property's full street address: number, street, city, state and ZIP. Each pricing option in the answer carries the label the term sheet prints for it (for example "Option A: lowest rate"); refer to options by that label. Read instant_term_sheet_requirements first for the fields.

Input Schema

TableJSON Schema

Name	Required	Description
`loan`	Yes	The loan.
`contact`	Yes	The investor: who the term sheet is for and where it is emailed.
`borrower`	Yes	The borrower.
`property`	Yes	The property.
`dscrInputs`	Yes	Rent and carrying costs: the debt service coverage ratio (DSCR) is computed from these.
`attestations`	Yes	The investor's three representations. A request that does not make all three is answered as out of scope and not priced.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / property / properties / acres / description

Previous value: -"Optional: the lot size, in acres. Left out, the deal cannot be priced instantly."New value: +"Optional: the lot size, in acres. Left out, the property is taken to be on 10 acres or less, and the term sheet says so. Give it where the property is on more than 10 acres, or where the borrower is a foreign national, since some programs for foreign nationals cap the lot at 2 acres."

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / loan / properties / prepayStructure / description

Previous value: -"Optional: the prepayment penalty's structure: fixed_5 (5% for the full term), fixed_3 (3% for the full term), declining (steps down over the term) or six_months_interest (six months' interest on the amount prepaid). Left out, the deal cannot be priced instantly."New value: +"Optional: the prepayment penalty's structure: fixed_5 (5% for the full term), fixed_3 (3% for the full term), declining (a penalty that declines over the term; the term sheet states how the lender that prices it calculates it) or six_months_interest (six months' interest on the amount prepaid). Left out, the deal cannot be priced instantly."

Changed3 schema fields changedSep 30, 2026

changedInput schema / properties / loan / properties / prepayStructure / description

Previous value: -"Optional: the prepayment penalty's structure: fixed_5 (5% for the full term), fixed_3 (3% for the full term), declining (steps down over the term) or six_months_interest (six months' interest on the amount prepaid). Ask the investor. Left out, the deal cannot be priced instantly."New value: +"Optional: the prepayment penalty's structure: fixed_5 (5% for the full term), fixed_3 (3% for the full term), declining (steps down over the term) or six_months_interest (six months' interest on the amount prepaid). Left out, the deal cannot be priced instantly."

changedInput schema / properties / loan / properties / prepayTermMonths / description

Previous value: -"Optional: the prepayment penalty term the investor wants, in months; 0 for none. One of 0, 6, 12, 24, 36, 48, 60. Ask the investor. Left out, the deal cannot be priced instantly."New value: +"Optional: the prepayment penalty term the investor wants, in months; 0 for none. One of 0, 6, 12, 24, 36, 48, 60. Left out, the deal cannot be priced instantly."

changedInput schema / properties / property / properties / acres / description

Previous value: -"Optional: the lot size, in acres. Ask the investor. Left out, the deal cannot be priced instantly."New value: +"Optional: the lot size, in acres. Left out, the deal cannot be priced instantly."

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / property / properties / county / description

Previous value: -"Optional: the county's five-digit FIPS code. Where a program restricts counties or cities, a request without it is confirmed by hand."New value: +"Optional: the county's five-digit FIPS code. A county you give is the one used. Left out, it is read from the ZIP code in the address; where a program restricts counties and the ZIP code does not settle which county, a request without it is confirmed by hand."

Changed3 schema fields changedSep 29, 2026

changedInput schema / properties / loan / properties / prepayStructure / description

Previous value: -"Optional: the prepayment penalty's structure: fixed_5 (5% for the full term), fixed_3 (3% for the full term), declining (steps down over the term) or six_months_interest (six months' interest on the amount prepaid)."New value: +"Optional: the prepayment penalty's structure: fixed_5 (5% for the full term), fixed_3 (3% for the full term), declining (steps down over the term) or six_months_interest (six months' interest on the amount prepaid). Ask the investor. Left out, the deal cannot be priced instantly."

changedInput schema / properties / loan / properties / prepayTermMonths / description

Previous value: -"Optional: the prepayment penalty term the investor wants, in months; 0 for none. One of 0, 6, 12, 24, 36, 48, 60."New value: +"Optional: the prepayment penalty term the investor wants, in months; 0 for none. One of 0, 6, 12, 24, 36, 48, 60. Ask the investor. Left out, the deal cannot be priced instantly."

changedInput schema / properties / property / properties / acres / description

Previous value: -"Optional: the lot size, in acres."New value: +"Optional: the lot size, in acres. Ask the investor. Left out, the deal cannot be priced instantly."

Changed4 schema fields changedSep 28, 2026

addedInput schema / properties / borrower / properties / firstTimeHomebuyer

Added value: +{
+  "description": "Optional: true where the borrower is a first-time homebuyer. Left out, the borrower is taken not to be one, and a term sheet that relies on that says so.",
+  "type": "boolean"
+}

changedInput schema / properties / dscrInputs / properties / monthlyRent / description

Previous value: -"The property's gross monthly rent, in dollars: the lease, or the market rent."New value: +"The property's gross monthly rent, in dollars: the lease, or the market rent. For a short-term rental, the 12-month average gross monthly rent."

addedInput schema / properties / loan / properties / ownershipMonths

Added value: +{
+  "description": "Refinances only, optional: how many months the borrower has owned the property. Left out, it is taken as at least 6 months, and a term sheet that relies on that says so.",
+  "minimum": 0,
+  "type": "number"
+}

changedInput schema / properties / property / properties / rentalType / description

Previous value: -"Optional: long_term for a lease, short_term for nightly or weekly rentals. Left out, the rent is read as long-term."New value: +"Optional: long_term for a lease, short_term for nightly or weekly rentals. Left out, the rent is read as long-term. For a short-term rental, give dscrInputs.monthlyRent as the 12-month average gross monthly rent."

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / property / properties / vacant

Added value: +{
+  "description": "Refinances only, optional: true where the property has no lease and no tenant. Left out, it is taken as rented, and a term sheet that relies on that says so.",
+  "type": "boolean"
+}

First observedSep 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Adds valuable context beyond annotations: describes the non-commitment nature ('indicative and not a commitment to lend'), the output delivery ('emailed to the investor with a private download link'), timing behavior, and how options are labeled in the response. It does not restate annotation hints but enriches understanding of the operation's semantics and outputs.

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?

Reasonably concise at five sentences, with key constraints front-loaded (purpose, timing, address requirement). The inclusion of option labeling is slightly tangential but still relevant. Could be tightened by merging the address sentence with the prerequisite statement.

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?

For a 6-parameter nested request tool with no output schema, the description covers the essential operational context: prerequisites, timing, non-commitment, delivery method, and option labeling. It stops short of describing what a successful response contains in detail, but that may be intentionally left to the output of instant_term_sheet_requirements.

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?

With 100% schema description coverage, the schema already thoroughly documents every parameter. The description adds little parameter-specific detail beyond reiterating the address requirement, which is already in the schema. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

States a specific verb and resource ('Request a written term sheet for a business-purpose loan on a non-owner-occupied 1–4 unit investment property'), including scope constraints. It distinguishes itself from the sibling instant_term_sheet_requirements by framing this as the actual request action versus reading requirements first.

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?

Explicitly directs the agent to 'Read instant_term_sheet_requirements first for the fields,' naming the prerequisite sibling. It also clarifies the timing expectation ('Instant where the deal fits the programs; otherwise an answer within 24 hours') and the condition for needing a full address on every request.

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

All Dominick Prevete: Instant Term Sheet 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?