Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_neft_rtgs_imps_charges

Read-onlyIdempotent

Calculate NEFT, RTGS, IMPS, and UPI transfer charges by amount, account type, and online status, including base charge, GST, and total for comparing payment modes.

Instructions

Calculate NEFT/RTGS/IMPS/UPI transaction charges.

Use when estimating bank transfer costs or comparing payment modes.

Args: transfer_mode: "NEFT", "RTGS", "IMPS", or "UPI" amount: Transfer amount in INR account_type: "savings" or "current" is_online: True if done via online banking

Returns: Charge breakdown with base charge, GST, and total.

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": {
      "transfer_mode": "<transfer_mode>",
      "amount": "<amount>"
    },
    "name": "calculate_neft_rtgs_imps_charges"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesTransfer amount in INR
is_onlineNoTrue if done via online banking
account_typeNo'savings' or 'current'savings
transfer_modeYesNEFT, RTGS, IMPS, or UPI
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26

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 / account_type / title
      Added value: +"Account Type"
    • addedInput schema / properties / amount / title
      Added value: +"Amount"
    • addedInput schema / properties / is_online / title
      Added value: +"Is Online"
    • addedInput schema / properties / transfer_mode / title
      Added value: +"Transfer Mode"
    • addedInput schema / title
      Added value: +"calculate_neft_rtgs_imps_chargesArguments"
    • addedOutput schema / title
      Added value: +"calculate_neft_rtgs_imps_chargesDictOutput"
  3. Addedv0.4.2

TDQS

A3.9/5.0
Behavior3/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 usefully adds the return structure ('base charge, GST, and total') but says nothing about which rate schedule/financial-year assumptions drive the numbers or how slab-based charges are applied.

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 and usage in the first two sentences, followed by a scannable Args/Returns block. Slight redundancy between the Args list and the already-described schema fields, but nothing is wasted.

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 deterministic read-only calculator with a full output schema and 100% schema coverage, the description covers purpose, trigger, inputs, and output shape adequately. The only real gap is the unmentioned financial_year parameter and the rate assumptions behind the computation.

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 description coverage is 100%, so the baseline is 3; the Args block largely restates the schema text verbatim without adding format or constraint detail (e.g., RTGS minimum thresholds, GST rate applied). It also omits the schema's 'financial_year' parameter entirely from the Args list, leaving that dimension undocumented in prose.

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 NEFT/RTGS/IMPS/UPI transaction charges') and enumerates the exact transfer modes covered. No sibling tool in the list performs transfer-cost calculation, so an agent can route here unambiguously.

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?

Explicitly says to use it 'when estimating bank transfer costs or comparing payment modes', which gives a clear triggering context. It stops short of naming when-not-to-use cases or an alternative tool, so it is not a full 5.

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