Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_gst

Read-onlyIdempotent

Compute GST breakdown with CGST/SGST or IGST split and optional cess for invoices, quotations, and compliance; supports back-calculating base from inclusive amounts.

Instructions

Calculate GST breakdown with CGST/SGST/IGST split and optional cess.

Use when computing tax for invoices, quotations, or GST compliance.

Args: amount: Base amount or GST-inclusive amount in rupees. gst_rate: Valid GST rate percentage. transaction_type: 'intra_state' or 'inter_state'. amount_includes_gst: Set True to back-calculate base. cess_category: For 28% items, specify applicable cess.

Returns: Standard envelope with base amount, CGST/SGST/IGST breakdown, cess amount, total GST, and total payable amount.

Notes: Rates are for general reference. Actual classification may vary.

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": {
      "amount": "<amount>",
      "gst_rate": "<gst_rate>",
      "transaction_type": "<transaction_type>"
    },
    "name": "calculate_gst"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesBase amount in rupees (or inclusive amount if flagged)
gst_rateYesGST rate as percentage: 0, 0.1, 0.25, 1.5, 3, 5, 12, 18, 28
cess_categoryNoCess category for 28% items. Default: 'default' (no cess)default
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
transaction_typeYes'intra_state' (CGST+SGST) or 'inter_state' (IGST)
amount_includes_gstNoIf True, back-calculate base from GST-inclusive amount

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. Changed8 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / amount / title
      Added value: +"Amount"
    • addedInput schema / properties / amount_includes_gst / title
      Added value: +"Amount Includes Gst"
    • addedInput schema / properties / cess_category / title
      Added value: +"Cess Category"
    • addedInput schema / properties / gst_rate / title
      Added value: +"Gst Rate"
    • addedInput schema / properties / transaction_type / title
      Added value: +"Transaction Type"
    • addedInput schema / title
      Added value: +"calculate_gstArguments"
    • addedOutput schema / title
      Added value: +"calculate_gstDictOutput"
  3. First observedv0.3.0

TDQS

A3.6/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 safety and determinism are covered structurally. The description adds the returned envelope contents and a caveat that rates are 'for general reference' with classification varying, which is genuine added context, but it says nothing about rounding, precision, or how cess categories are resolved beyond the 28% note.

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?

It is front-loaded with the one-line purpose, then cleanly sectioned into usage, Args, Returns and Notes. The Args block is partly redundant with a 100%-covered schema, and the Returns block duplicates the existing output schema, so a bit of the text doesn't earn its place.

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 calculator with a full output schema, the definition covers purpose, inputs, output shape and a caveat about rate applicability, which is sufficient to call it correctly. The only shortfall is the undocumented financial_year parameter and the missing precision/rounding behavior.

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 documents all six parameters, and the Args block largely restates it. The one place the description adds meaning is 'cess_category: For 28% items', and it slightly weakens gst_rate by saying only 'valid GST rate percentage' where the schema enumerates the allowed values. It also omits financial_year from the Args list entirely, so the description does not fully match the schema.

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 gives a specific verb and resource — calculate a GST breakdown with CGST/SGST/IGST split and optional cess — which is concrete enough to distinguish it from the many validators and from calculate_gst_late_fee in the sibling list. It doesn't explicitly name an alternative tool, so it stops short of full sibling differentiation.

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?

The line 'Use when computing tax for invoices, quotations, or GST compliance' gives a clear use context that an agent can match against a task. It offers no exclusions or 'use X instead' routing, particularly against calculate_gst_late_fee or lookup_hsn_code, which is a real gap in a 60+ tool namespace.

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