Skip to main content
Glama

SecureLend Market

by ai.securelend.mcp
OverviewDiscussionsAdmin

calculate_mortgage_payment

Calculate PITI mortgage payments including property taxes and insurance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states that the calculation includes property taxes and insurance, but does not disclose whether those are estimated, user-supplied, or how the result is returned. There is no mention of assumptions, exclusions, or output behavior.

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?

The description is a single, focused sentence with no filler or repetition. The key action and scope are front-loaded, and every word contributes meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and no parameter definitions, the description is too sparse to fully support correct invocation. An agent would need to infer what inputs to supply (loan amount, interest rate, term, tax amount, insurance amount) and what the expected output format is.

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

Parameters4/5

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

The schema has no defined parameters, so per the baseline rule for zero parameters, the description gets a 4. It adds some semantic meaning by indicating that property taxes and insurance are part of the calculation, but it does not enumerate the actual inputs expected.

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?

The description uses a specific verb ('Calculate') and a specific resource ('PITI mortgage payments' including property taxes and insurance). This clearly distinguishes it from the many compare_* tools and from calculate_loan_payment, which is general loan amortization rather than mortgage PITI.

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?

The description gives no explicit guidance about when to use this tool versus alternatives such as calculate_loan_payment or compare_personal_mortgages. Usage is only weakly implied by the word 'Calculate', and no exclusions or alternative conditions are provided.

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