Skip to main content
Glama

Calculate loan EMI

calculate_emi
Read-only

Calculates the monthly EMI (equated monthly instalment) for a loan from the principal, annual interest rate and tenure in months, plus total interest and total payment.

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>",
      "annualRate": "<annualRate>",
      "months": "<months>"
    },
    "name": "calculate_emi"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYesLoan tenure in months (1-600).
principalYesLoan amount (principal), greater than 0.
annualRateYesAnnual interest rate in percent (0 or more).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered and the description need only add computation semantics. It does add value by stating the return content (EMI, total interest, total payment), which goes beyond the annotations without contradicting them.

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 a clear verb, inputs and outputs, and no filler. It could be split for scannability, but nothing is wasted.

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

Completeness3/5

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

For a 3-parameter pure calculator with full schema coverage and read-only annotations, the definition covers the essentials. It omits the formula's assumptions (fixed rate, monthly compounding, no fees) and any output precision or currency handling, which would matter to an agent interpreting results, and no output schema exists to fill that gap.

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% and the schema already defines types, bounds and meanings for principal, annualRate and months, so the baseline is 3. The description only restates the same three inputs in prose and adds nothing new — no note on rate units beyond the schema, no rounding or sign conventions.

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 computation and its inputs and outputs: monthly EMI from principal, annual rate and tenure in months, plus total interest and total payment. It clearly distinguishes itself from the utility siblings (count_words, format_json, generate_password, generate_qr_code), though it doesn't explicitly say it's non-financial-advice or point to alternatives.

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 by the domain — a loan amortization calculation — but there's no explicit when-to-use or when-not-to-use guidance, no caveat about assumptions (fixed rate, no fees, no prepayment). For a simple single-purpose calculator this is largely adequate, but it stops at implicit context.

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