Skip to main content
Glama

Business Calculator: GST, Margin & Everyday Formulas

GST, TDS / TCS & Invoice Calculators — Saifs AI

gst_tds_invoice_calculators
Read-only

Calculate Indian GST, TDS / TCS and invoice totals exactly: split ₹1,180 into base + GST, add GST, CGST + SGST / UTGST vs IGST by place of supply or GSTIN, reverse charge, GST slabs on a date (GST 2.0: 5 / 18 / 40); TDS by section with threshold check (194C, 194H, 194I, 194J, 194Q, 194T ...; Income-tax Act 2025 s.393 from 1-Apr-2026), TCS (s.394 rates from 1-Apr-2026); invoice lines → discount → GST → round-off → amount in words; convert currency at a rate you supply. Returns a standard-library Python script with only these calculators (gst_calculator, tds_tcs_calculator, invoice_calculator, currency_converter) to run in your code sandbox; each answer gives result, formula, inputs used, rounding, rule version and effective date. Inputs: tools (narrow to some of these calculators), calls ([{tool, operation, inputs, rounding?, as_of?}] baked into the script; a calculator from another area named in calls is added), calls_path (JSON file of calls in your sandbox). Calculation never runs on this server or any API. Not for EMI / interest / NPV / IRR (refused), nor HSN classification, filing returns, salary TDS, live FX rates, interest. Operation and input names: business_calculator_list_formulas.

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_tds_invoice_calculators"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsNoCalculations to bake into the script (their calculators are included).
toolsNoNarrow the script to some of this area's calculators (default: all of them).
calls_pathNoJSON file of calls already in your sandbox.
full_catalogNoKeep descriptions and worked examples inside the script (larger).

Output Schema

NameRequiredDescriptionDefault
areaNo
notesNo
scriptYes
languageNo
requiresNo
calls_pathNo
operationsNo
call_formatNo
instructionsYes
writes_filesNo
calls_baked_inNo
engine_versionYes
included_toolsYes
server_computesNo
network_access_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover read-only/non-destructive/closed-world, but the description adds the crucial behavior that nothing executes server-side or via any API — it emits a script — plus that each answer returns result, formula, inputs used, rounding, rule version and effective date. It even discloses the edge case that a calculator from another area named in 'calls' is silently added.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and execution model are front-loaded, but the middle is a dense semicolon run of GST/TDS section enumerations and the exclusion list repeats 'interest' twice. Some rate-version detail could be trimmed without losing selection signal.

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?

An output schema exists, yet the description still explains the answer shape, and it fully covers the sandbox execution model, scope narrowing, dated rule versions, and what is refused. Nothing an agent needs to invoke it correctly appears missing.

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 100%, so the parameters are already documented; the description goes modestly beyond by explaining the intent of 'tools' (narrow to some calculators), 'calls' (baked into the script), and 'calls_path' (JSON file already in the sandbox). The cross-area inclusion behavior is meaning the schema does not convey.

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 specific verbs and resources — GST split/add, CGST/SGST vs IGST by place of supply, TDS by section with threshold check, TCS, invoice line build-up, currency conversion — and names the four underlying calculators (gst_calculator, tds_tcs_calculator, invoice_calculator, currency_converter). It also clarifies the delivery mechanism: it returns a standard-library Python script to run in a sandbox. This clearly separates it from business_calculator_list_formulas and the other *_calculators siblings.

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

Usage Guidelines5/5

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

Gives explicit when-not guidance with refusals (EMI / interest / NPV / IRR, HSN classification, filing returns, salary TDS, live FX rates) and points to the alternative for operation/input names (business_calculator_list_formulas). It also explains how to narrow scope via 'tools' and how to bake calls in via 'calls' vs 'calls_path'.

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.