Skip to main content
Glama
Sign In

SecureLend Market

by ai.securelend.mcp
OverviewDiscussionsAdmin

Calculate mortgage payment

calculate_mortgage_payment
Read-only

Calculate PITI mortgage payments including property taxes and insurance

Input Schema

NameRequiredDescriptionDefault
insuranceNo
principalNo
annualRateNo
loanAmountNo
termMonthsNo
propertyTaxNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedInput schema / properties
      Added value: +{
+  "annualRate": {
+    "type": "number"
+  },
+  "insurance": {
+    "type": "number"
+  },
+  "loanAmount": {
+    "type": "number"
+  },
+  "principal": {
+    "type": "number"
+  },
+  "propertyTax": {
+    "type": "number"
+  },
+  "termMonths": {
+    "type": "number"
+  }
+}
  2. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +true
    • removedInput schema / properties
      Removed value: -{
-  "downPayment": {
-    "description": "The amount paid upfront in USD.",
-    "minimum": 0,
-    "type": "number"
-  },
-  "homeInsurance": {
-    "description": "The annual home insurance cost in USD.",
-    "minimum": 0,
-    "type": "number"
-  },
-  "interestRate": {
-    "description": "The annual interest rate (e.g., 3.5 for 3.5%).",
-    "minimum": 0,
-    "type": "number"
-  },
-  "loanTermInYears": {
-    "description": "The duration of the loan in years.",
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  },
-  "propertyTaxRate": {
-    "description": "The annual property tax rate as a percentage (e.g., 1.2 for 1.2%).",
-    "minimum": 0,
-    "type": "number"
-  },
-  "propertyValue": {
-    "description": "The total value of the property in USD.",
-    "exclusiveMinimum": 0,
-    "type": "number"
-  }
-}
    • removedInput schema / required
      Removed value: -[
-  "propertyValue",
-  "downPayment",
-  "interestRate",
-  "loanTermInYears",
-  "propertyTaxRate",
-  "homeInsurance"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "loanAmount": {
-      "description": "The total loan amount after down payment.",
-      "type": "number"
-    },
-    "monthlyHomeInsurance": {
-      "description": "The estimated monthly home insurance payment.",
-      "type": "number"
-    },
-    "monthlyPropertyTax": {
-      "description": "The estimated monthly property tax payment.",
-      "type": "number"
-    },
-    "principalAndInterest": {
-      "description": "The monthly payment for principal and interest.",
-      "type": "number"
-    },
-    "totalMonthlyPayment": {
-      "description": "The total estimated monthly payment (PITI).",
-      "type": "number"
-    }
-  },
-  "required": [
-    "loanAmount",
-    "principalAndInterest",
-    "monthlyPropertyTax",
-    "monthlyHomeInsurance",
-    "totalMonthlyPayment"
-  ],
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. Beyond that the description only names the PITI components; it omits critical behavioral facts such as the assumed rate format, whether the result is monthly or total, and how 'principal' and 'loanAmount' differ — a genuine trap given both exist as parameters.

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

Conciseness3/5

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

A single, front-loaded sentence with no padding, so it is concise. However, brevity here tips into under-specification: it spends its words restating the acronym rather than resolving ambiguity in the inputs.

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?

Placeholder — see corrected value in summary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters, so the description must compensate and largely does not. Only propertyTax and insurance are implicitly covered; annualRate (percent vs decimal), termMonths (unit), and the redundant-looking principal/loanAmount pair are undocumented anywhere.

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 verb ('Calculate') and resource ('PITI mortgage payments'), and 'PITI' plus 'including property taxes and insurance' clearly signals a mortgage-payment calculator rather than a generic loan calculator. It does not explicitly distinguish itself from the sibling calculate_loan_payment, so the agent must infer the difference.

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

Usage Guidelines2/5

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

No guidance on when to use this versus calculate_loan_payment or compare_business_mortgages, and no stated preconditions. The agent is left to infer usage purely from the tool name and the word 'mortgage'.

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

All SecureLend Market 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