Skip to main content
Glama
bangladesh-mcp

bangladesh-mcp

by sarif-mia

loan_emi

Read-onlyIdempotent

Calculate equal monthly installments and total interest for a BDT loan from principal, annual interest rate, and term in months.

Instructions

Equal monthly instalment (EMI) for a loan, with total interest.

Args: principal: Loan amount in BDT. annual_rate_percent: Yearly interest rate, e.g. 12 for 12%. months: Loan term in months.

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_rate_percent": "<annual_rate_percent>",
      "months": "<months>"
    },
    "name": "loan_emi"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
principalYes
annual_rate_percentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds that the result includes total interest, which is a small but real behavioral detail beyond annotations, but says nothing about rounding, currency of the output, or edge cases such as zero rate.

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 core output is front-loaded in one sentence, followed by a compact parameter list. Nothing is padded, and given the empty schema descriptions, the Args block earns its space.

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?

An output schema exists, so the return values need not be explained, and all three parameters are documented with units. For a simple pure-computation tool this is nearly sufficient; only edge-case behavior and the alternative-shot of calculate_expression are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and does so: 'principal' is specified as a loan amount in BDT, 'annual_rate_percent' is given a concrete format example (12 for 12%), and 'months' is identified as the loan term. Units and format are meaningfully clarified. It falls short of describing valid ranges or what happens with a 0% or 0-month input.

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?

States a specific computation and resource: 'Equal monthly instalment (EMI) for a loan, with total interest.' An agent can tell this apart from domain-different siblings such as income_tax or savings_growth, though there is no explicit naming of the generic calculate_expression alternative.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no statement of what the tool is not for. The agent must infer that this is the right choice from the name and the calculation description alone.

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