Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculate_emi

Read-onlyIdempotent

Calculate a loan's monthly EMI with year-by-year amortization. Enter principal, rate, and tenure to get total interest and payment details for comparing loans or planning prepayments.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loan_typeNoLoan type: home, personal, car, education, otherother
principalYesLoan amount in INR
tenure_monthsYesLoan tenure in months
annual_interest_rateYesAnnual interest rate as percentage (e.g., 8.5)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Addedv0.4.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds valuable context: 'standard reducing balance formula', a lender-variance caveat, and the year-by-year schedule detail. No contradiction with annotations.

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 well-organized with clear headings, front-loaded usage guidance, and concise parameter notes. Every sentence is purposeful and there is no redundancy.

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

Completeness5/5

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

Given the read-only annotations and full output schema, the description provides all needed context: use cases, formula, caveats, and parameter constraints. The tool can be invoked correctly without missing information.

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 schema already documents all parameters clearly. The description adds only minor extras like tenure max 360 and the loan_type label, which slightly improves clarity but does not fully warrant more than the baseline.

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?

States a specific verb and resource: 'Calculate EMI for a loan with year-by-year amortization schedule.' It also distinguishes itself from the many sibling calculators by emphasizing the amortization schedule, which is unique enough.

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?

Provides explicit usage contexts: 'Use when computing loan EMIs, comparing loan options, or planning prepayment strategies.' However, it does not mention when to avoid using it or explicitly point to an alternative tool.

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