Skip to main content
Glama

Loan EMI

calculate_loan_emi
Read-onlyIdempotent

Monthly EMI, total interest and total repayment for a home, car or personal loan in India (reducing-balance method, monthly rests). Optional part-payments (a yearly amount, and a one-time amount in a chosen year) keep the EMI and shorten the loan, as banks do by default; the result then shows the interest saved and when the loan ends.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "principal": "<principal>",
      "annual_interest_rate": "<annual_interest_rate>",
      "tenure_years": "<tenure_years>"
    },
    "name": "calculate_loan_emi"
  }
}

Input Schema

NameRequiredDescriptionDefault
principalYesLoan amount in rupees
tenure_yearsYesLoan tenure in years
yearly_part_paymentNoOptional extra payment made with every 12th EMI, in rupees (default 0)
annual_interest_rateYesInterest rate, % per year (8.5 means 8.5%)
one_time_part_paymentNoOptional one-time extra payment, in rupees (default 0)
one_time_part_payment_yearNoYear whose last EMI the one-time payment is made with (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / one_time_part_payment
      Added value: +{
      +  "description": "Optional one-time extra payment, in rupees (default 0)",
      +  "maximum": 100000000,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / one_time_part_payment_year
      Added value: +{
      +  "description": "Year whose last EMI the one-time payment is made with (default 5)",
      +  "maximum": 30,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / yearly_part_payment
      Added value: +{
      +  "description": "Optional extra payment made with every 12th EMI, in rupees (default 0)",
      +  "maximum": 50000000,
      +  "minimum": 0,
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description correctly spends its space elsewhere: it discloses the critical semantic that part-payments keep the EMI constant and shorten tenure 'as banks do by default', and that the result additionally reports interest saved and the payoff date. The only gap is that it does not state rounding/currency assumptions or the output structure beyond listing outputs.

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?

Two sentences, front-loaded with the primary output and method, then the optional part-payment behavior. Dense but every clause carries information; only slight tightening (e.g. spelling out the default year) could improve it.

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 six parameters, no output schema, and safe read-only annotations, the description covers what the tool returns, the calculation basis, and the non-obvious part-payment semantics — enough for an agent to call it correctly. Missing only edge-case handling (part-payment larger than outstanding balance, chosen year beyond tenure).

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 coverage is 100%, so the baseline is 3. The description does add a bit beyond the schema by explaining that the yearly and one-time part-payments interact with tenure rather than reducing the EMI, but it does not clarify the default one_time_part_payment_year=5 fallback or what happens when the chosen year exceeds tenure_years.

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 the concrete outputs (monthly EMI, total interest, total repayment), the loan types covered (home, car, personal), and the exact method (reducing-balance, monthly rests), so an agent knows precisely what is computed. It stops short of naming a sibling like flat_vs_reducing_rate_calculator, which is the one nearby tool an agent might confuse it with.

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?

Usage is implied rather than stated: the loan-type list and the India/reducing-balance qualifier frame when the tool applies. There is no explicit when-not guidance and no routing to alternatives such as flat_vs_reducing_rate_calculator or home_loan_affordability, so the agent must infer the boundary.

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