SecureLend Market

Calculate loan payment

calculate_loan_payment

Read-only

Calculate monthly loan payments with principal, interest, and total cost breakdown

Input Schema

Name	Required	Description
`rate`	No
`term`	No
`amount`	No
`principal`	No
`annualRate`	No	Annual rate as a decimal, for example 0.06.
`loanAmount`	No
`termMonths`	No
`loanTermInMonths`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties

Added value: +{
+  "amount": {
+    "type": "number"
+  },
+  "annualRate": {
+    "description": "Annual rate as a decimal, for example 0.06.",
+    "type": "number"
+  },
+  "loanAmount": {
+    "type": "number"
+  },
+  "loanTermInMonths": {
+    "type": "number"
+  },
+  "principal": {
+    "type": "number"
+  },
+  "rate": {
+    "type": "number"
+  },
+  "term": {
+    "type": "number"
+  },
+  "termMonths": {
+    "type": "number"
+  }
+}

Changed5 schema fields changedSep 23, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +true
```

removedInput schema / properties

Removed value: -{
-  "interestRate": {
-    "description": "The annual interest rate (e.g., 5 for 5%).",
-    "minimum": 0,
-    "type": "number"
-  },
-  "loanAmount": {
-    "description": "The total amount of the loan in USD.",
-    "exclusiveMinimum": 0,
-    "type": "number"
-  },
-  "loanTermInMonths": {
-    "description": "The duration of the loan in months.",
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  }
-}

removedInput schema / required

Removed value: -[
-  "loanAmount",
-  "interestRate",
-  "loanTermInMonths"
-]

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "monthlyPayment": {
-      "description": "The calculated monthly payment amount.",
-      "type": "number"
-    },
-    "totalInterest": {
-      "description": "The total interest paid over the life of the loan.",
-      "type": "number"
-    },
-    "totalPayment": {
-      "description": "The total amount to be paid over the life of the loan.",
-      "type": "number"
-    }
-  },
-  "required": [
-    "monthlyPayment",
-    "totalPayment",
-    "totalInterest"
-  ],
-  "type": "object"
-}New value: +null

First observedMay 27, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare a safe, read-only, closed-world calculation, so the safety profile is covered. The description adds useful behavior by naming the returned breakdown, but it says nothing about response format, assumptions (e.g., amortization, monthly compounding, rounding), or what happens with the many unset parameters.

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?

A single front-loaded sentence with no filler. It is efficient, though it is short enough that it leaves the major ambiguities unaddressed.

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?

For an 8-parameter, zero-required calculator with no output schema, the description omits parameter guidance, which values take precedence, and the shape of the cost breakdown. An agent could call it, but would likely guess wrong about which fields to populate.

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 only 13% — just annualRate — and 8 parameters are all optional. The description does not disambiguate the overlapping sets (rate vs annualRate, amount vs principal vs loanAmount, term vs termMonths vs loanTermInMonths) or clarify units, so it fails to compensate for the schema gap.

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?

The description names a specific verb and resource (calculate monthly loan payments) and previews the output (principal, interest, total cost). It is clear on its own, but does not differentiate itself from the very similar sibling calculate_mortgage_payment or say when a loan differs from a mortgage.

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?

There is no statement of when to use this tool versus calculate_mortgage_payment or the compare_* loan tools, and no prerequisites or exclusions. The agent has to infer usage from the name alone.

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

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