Skip to main content
Glama

Loan Calculator API - monthly payment and full amortization schedule

loan_calculator
Read-onlyIdempotent

Annuity or equal-principal loans: monthly payment, total interest, total paid and the month-by-month schedule (also as xlsx/csv), optional extra monthly payment. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.002 per call via x402 at https://radarbg.com/x402/loan-calculator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "years": 5,
      "amount": 20000,
      "ratePercent": 6.5
    },
    "name": "loan_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoannuity or equal (equal principal)annuity
yearsNoYears
amountNoLoan amount
monthsNoPlus months
ratePercentNoYearly interest rate in %
extraMonthlyNoExtra payment each month (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / months / minimum
      Added value: +0
    • addedInput schema / properties / years / minimum
      Added value: +0
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint/openWorldHint annotations, the description discloses that computation happens on the vendor's server, that generated files are deleted immediately with nothing stored, and states concrete rate limits (25 calls/day per IP) plus the x402 paid path. These are exactly the privacy, cost, and throughput facts an agent needs before invoking a remote compute service.

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?

Three sentences, front-loaded with the computation and outputs, followed by hosting/retention, then limits and pricing. No sentence is redundant and nothing important is buried.

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?

With no output schema, the description does the work of naming the return values and the downloadable file formats, and it covers hosting, retention, rate limits, and pricing for a stateless remote calculator. Minor gaps remain around error behavior and what the schedule records contain, but the essentials for correct invocation are present.

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?

Schema description coverage is 100%, so the six parameters are already documented in the input schema, including defaults and the annuity/equal enum. The description only restates the extra-monthly-payment option and adds no syntax, interaction, or edge-case meaning beyond the schema, so the baseline of 3 applies.

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 names both supported loan models (annuity, equal-principal) and enumerates concrete outputs: monthly payment, total interest, total paid, month-by-month schedule, and xlsx/csv export. That level of specificity separates it from a generic interest calculator among the siblings without needing to name one.

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

Usage Guidelines3/5

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

The tool's usage is implied rather than stated: an agent can infer it computes loan repayment figures, and it notes the optional extra monthly payment. There is no explicit when-to-use or when-not-to-use guidance relative to alternatives such as compound_interest_calculator, and the free/paid tier text is operational rather than routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources