Skip to main content
Glama
bangladesh-mcp

bangladesh-mcp

by sarif-mia

savings_growth

Read-onlyIdempotent

Calculate the future value of a lump sum plus monthly deposits in BDT, compounded monthly, to project DPS or FDR maturity amounts.

Instructions

Future value of a lump sum plus monthly deposits (DPS/FDR), compounded monthly.

Args: principal: Starting amount in BDT (0 for a plain DPS). monthly_deposit: Amount deposited every month in BDT. annual_rate_percent: Yearly interest rate, e.g. 9 for 9%. months: Number of 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>",
      "monthly_deposit": "<monthly_deposit>",
      "annual_rate_percent": "<annual_rate_percent>",
      "months": "<months>"
    },
    "name": "savings_growth"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
principalYes
monthly_depositYes
annual_rate_percentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a pure, read-only, idempotent, closed-world calculation, so the safety profile needs no restatement. The description adds the key behavioral fact that compounding is monthly, but omits meaningful calculation conventions the agent might need — whether deposits land at the start or end of each month, whether the annual rate is nominal or effective, and how rounding is handled.

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?

One front-loaded summary sentence, then a compact Args block with one line per parameter and no filler. The docstring-style layout is standard and scannable, though the sentence and the Args block slightly duplicate the parameter meanings.

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 return values need no explanation, and all four required parameters are given meaning despite 0% schema coverage. The remaining gap is calculation convention (deposit timing, rate interpretation) for a tool that is otherwise well specified.

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 description coverage is 0%, so the description carries the whole burden, and it does: all four parameters are explained with units and semantics (BDT amounts, annual rate percent with a concrete '9 for 9%' example, month count, and the 0-principal DPS case). Only the timing convention for monthly_deposit is left undefined, which prevents a 5.

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 — future value of a lump sum plus monthly deposits, compounded monthly — which is far more informative than the bare name 'savings_growth'. It does not explicitly contrast itself with the numeric siblings (loan_emi, income_tax), so sibling differentiation is left implicit, but the purpose itself is unambiguous.

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?

There is no statement of when to use this versus alternatives such as loan_emi or income_tax. The only guidance-like content is the inline note 'principal: 0 for a plain DPS', which is a parameter hint rather than a usage policy, and no exclusions or prerequisites are given.

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