Mortgage Calculation for AI Agents
The tool
Give enterprise agents mortgage payment math through the same real-data layer, returning monthly payment and interest breakdowns on demand.
Once your client is connected to the VerveContext MCP server, this appears in its tool list as MortgageCalculationforAIAgents. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.
{
"name": "MortgageCalculationforAIAgents",
"arguments": {
"amount": "200000",
"rate": "4.5",
"years": "30"
}
}What that looks like in a conversation
You don't name the tool — the model picks it. Asking about 200000 in the terms this source covers is enough for it to reach for MortgageCalculationforAIAgents on its own.
Connecting
One server URL covers every source in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp"
}
}
}https://api.vervecontext.com/v1/mcpPer-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.
| Argument | Type | Example | Description |
|---|---|---|---|
amountRequired | number | 200000 | The loan amount |
rateRequired | number | 4.5 | The interest rate (percentage) |
yearsRequired | integer | 30 | The loan term in years |
downpayment | number | 15000 | The down payment amount |
annual_propertytax | number | 2000 | The annual property tax amount |
annual_homeinsurance | number | 1200 | The annual home insurance amount |
annual_hoa | number | 500 | The annual HOA amount |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"amount": 570000,
"downpayment": 0,
"rate": 6.8,
"years": 30,
"total_interest_paid": 767750.49,
"total_loan_payment": 1337750.49,
"interestRatio": 57.39,
"monthly_payment": {
"total": 3715.97,
"mortgage": 3715.97,
"property_tax": 0,
"hoa": 0,
"home_insurance": 0
},
"annual_payment": {
"total": 44591.68,
"mortgage": 44591.68,
"property_tax": 0,
"hoa": 0,
"home_insurance": 0
},
"formatted": {
"amount": "$570,000",
"monthlyPayment": "$3,715.97",
"totalInterestPaid": "$767,750.49",
"totalLoanPayment": "$1,337,750.49"
},
"amortization_schedule": [
{
"month": 1,
"interest_payment": 3230,
"principal_payment": 485.97,
"remaining_balance": 569514.03
},
{
"month": 2,
"interest_payment": 3227.25,
"principal_payment": 488.73,
"remaining_balance": 569025.3
},
{
"month": 3,
"interest_payment": 3224.48,
"principal_payment": 491.5,
"remaining_balance": 568533.8
}
]
}
}Fields
| Field | Type | Example | Description |
|---|---|---|---|
amount | number | Loan amount in dollars | |
downpayment | number | Down payment amount provided | |
rate | number | Interest rate percentage used for calculation | |
years | number | Loan term in years | |
total_interest_paidPremium | number | Total interest paid over entire loan term | |
total_loan_paymentPremium | number | Total amount paid (principal + interest) | |
interestRatioPremium | number | Percentage of payment that is interest | |
monthly_payment | object | ||
└ monthly_payment.total | number | Total monthly payment including all fees | |
└ monthly_payment.mortgage | number | Monthly mortgage payment (principal + interest) | |
└ monthly_payment.property_tax | number | Monthly property tax portion of payment | |
└ monthly_payment.hoa | number | Monthly HOA fee portion of payment | |
└ monthly_payment.home_insurance | number | Monthly home insurance portion of payment | |
annual_payment | object | ||
└ annual_payment.total | number | Total annual payment including all fees | |
└ annual_payment.mortgage | number | Annual mortgage payment (principal + interest) | |
└ annual_payment.property_tax | number | Annual property tax portion of payment | |
└ annual_payment.hoa | number | Annual HOA fee portion of payment | |
└ annual_payment.home_insurance | number | Annual home insurance portion of payment | |
formatted | object | ||
└ formatted.amount | string | Formatted loan amount with currency symbol | |
└ formatted.monthlyPayment | string | Formatted monthly payment with currency | |
└ formatted.totalInterestPaid | string | Formatted total interest paid with currency | |
└ formatted.totalLoanPayment | string | Formatted total loan payment with currency | |
amortization_schedulePremium | array[3] | Month-by-month loan repayment schedule breakdown | |
└ amortization_schedule.0.monthPremium | number | Payment month number in loan term | |
└ amortization_schedule.0.interest_paymentPremium | number | Interest portion of monthly payment | |
└ amortization_schedule.0.principal_paymentPremium | number | Principal portion of monthly payment | |
└ amortization_schedule.0.remaining_balancePremium | number | Outstanding loan balance after payment |
Why ground on it
A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value with a shape you can check, which is the difference between an answer you can cite and one you have to hedge.
Point an evaluation at monthly_payment.total: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.
Failure modes
Errors come back as tool errors with a sentence the model can act on, not a bare status code.
| Status | What it means |
|---|---|
400 / 422 | The arguments didn't validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Out of credits. Not a bad key — the month's allowance is spent. |
404 | This source isn't part of VerveContext. Check the catalog. |
429 | Brief rate limit. Retrying after a moment succeeds. |
Other ways to use Mortgage Calculation for AI Agents
Set up Mortgage Calculation for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.
Frequently asked questions
Do I have to tell the agent to use MortgageCalculationforAIAgents?
No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.
Does connecting the server expose every tool at once?
Yes — one connection lists the whole VerveContext catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.
What does a call cost?
1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.
Is there a REST version of this?
Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.