Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_emi

Read-onlyIdempotent

Compute loan EMIs and view year-by-year amortization schedules to compare loan options or plan prepayments using principal, annual interest rate, and tenure in months.

Instructions

Calculate EMI for a loan with year-by-year amortization schedule.

Use when computing loan EMIs, comparing loan options, or planning prepayment strategies.

Args: principal: Loan amount in INR. annual_interest_rate: Annual rate as percentage. tenure_months: Loan tenure in months (max 360). loan_type: Label for the loan type.

Returns: Standard envelope with EMI, total payment, interest, and amortization.

Notes: Uses standard reducing balance formula. Actual EMI may vary by lender.

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_months": "<tenure_months>"
    },
    "name": "calculate_emi"
  }
}

Input Schema

NameRequiredDescriptionDefault
loan_typeNoLoan type: home, personal, car, education, otherother
principalYesLoan amount in INR
tenure_monthsYesLoan tenure in months
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
annual_interest_rateYesAnnual interest rate as percentage (e.g., 8.5)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / financial_year
      Added value: +{
      +  "default": "2025-26",
      +  "description": "Financial year (e.g. '2025-26', '2026-27')",
      +  "title": "Financial Year",
      +  "type": "string"
      +}
  2. Changed7 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / annual_interest_rate / title
      Added value: +"Annual Interest Rate"
    • addedInput schema / properties / loan_type / title
      Added value: +"Loan Type"
    • addedInput schema / properties / principal / title
      Added value: +"Principal"
    • addedInput schema / properties / tenure_months / title
      Added value: +"Tenure Months"
    • addedInput schema / title
      Added value: +"calculate_emiArguments"
    • addedOutput schema / title
      Added value: +"calculate_emiDictOutput"
  3. Addedv0.4.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: the reducing-balance formula used, the caveat that actual EMI may vary by lender, and the 360-month tenure ceiling. It does not discuss rounding/precision or how financial_year affects the schedule.

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?

Front-loaded with purpose before the Args/Returns/Notes sections, so an agent can stop reading early. The Args block largely duplicates the schema descriptions, which is mild waste, but nothing is padded or unclear.

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?

For a read-only calculator with an output schema, the definition covers purpose, triggers, formula basis, and assumptions adequately. The one genuine gap is the undocumented financial_year parameter, and the Returns section is redundant given the output schema exists.

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?

With 100% schema description coverage the schema already documents all five parameters, so the baseline is 3. The description adds one useful constraint not in the schema (tenure max 360) but otherwise restates the schema, and it omits the fifth parameter, financial_year, entirely.

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 first sentence names a specific verb and resource (calculate / EMI for a loan) plus a distinctive capability (year-by-year amortization schedule), which separates it from the many validation and other calculator siblings. It does not explicitly name a sibling it is not, so it stops short of a 5.

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

Usage Guidelines4/5

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

The 'Use when...' sentence gives three concrete triggering scenarios: computing EMIs, comparing loan options, and planning prepayment strategies. There are no when-not conditions or named alternatives (e.g. versus calculate_home_vs_rent or calculate_sip_returns), so it is clear context without exclusions.

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

Deploy Server

Other Tools