Skip to main content
Glama

GST Calculator

gst_calculator
Read-onlyIdempotent

Add or remove GST for any rate and amount. Same calculation as https://paisafinder.com/calculators/gst-calculator. Every input is optional; anything left out uses the default shown in its schema.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gst_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoAmount (rupees)
modeNoWhat do you want to do?: 0 = Add GST, 1 = Remove GST. Add GST to a price before tax, or take it out of a price that includes GST
rateNoGST rate (%). Since 22 Sep 2025: 5% / 18%, and 40% for luxury and sin goods

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"Mode (0=Add 1=Remove). 0 = add GST to a net price · 1 = extract GST from a gross price"New value: +"What do you want to do?: 0 = Add GST, 1 = Remove GST. Add GST to a price before tax, or take it out of a price that includes GST"
    • addedInput schema / properties / mode / enum
      Added value: +[
      +  0,
      +  1
      +]
    • removedInput schema / properties / mode / maximum
      Removed value: -1
    • removedInput schema / properties / mode / minimum
      Removed value: -0
  2. Changed2 schema fields changed
    • changedInput schema / properties / rate / description
      Previous value: -"GST rate (%). Common: 5 / 12 / 18 / 28"New value: +"GST rate (%). Since 22 Sep 2025: 5% / 18%, and 40% for luxury and sin goods"
    • changedInput schema / properties / rate / maximum
      Previous value: -28New value: +40
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely useful context beyond them: every input is optional and omitted inputs fall back to schema defaults, meaning an agent can call with zero arguments and still get a result. It omits any statement about the shape of the returned figure, which is the main remaining gap.

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?

Three short sentences, front-loaded with the operation before the reference link and the defaults note. The external URL is arguably filler for an agent that cannot fetch it, but it does pin the exact calculation convention the tool follows.

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?

For a three-parameter pure calculator with full schema coverage, no output schema needed, and annotations covering the safety profile, the description covers purpose, default behavior, and the semantic split between modes. Nothing an agent needs to invoke it correctly is missing.

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 schema already explains amt, mode, and rate including the mode enum semantics and the post-Sep-2025 rate bands. The description only points back at the schema for defaults and adds no syntax, unit, or edge-case detail beyond it, so the baseline of 3 applies.

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 opens with a specific verb pair and resource: "Add or remove GST for any rate and amount," which tells an agent exactly what the tool computes. It does not name or differentiate itself from any sibling, though GST is distinct enough from the tax/interest calculators listed that confusion risk is low.

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?

The description supplies the conceptual distinction between the two modes (a pre-tax price vs a GST-inclusive price), which is real guidance for choosing a parameter value. It gives no when-to-use/when-not-to-use framing relative to other calculators and no prerequisites, so usage is only implied.

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