Skip to main content
Glama

TrueCalci

by com.truecalci
OverviewDiscussionsAdmin

India GST composition scheme

gst_composition
Read-onlyIdempotent

Calculate statutory GST quarterly tax liabilities under the Composition Scheme (Section 10 of CGST Act). Computes applicable turnover tax for traders (1%), manufacturers (1%), and restaurant service providers (5%), enforcing statutory turnover thresholds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoComposition scheme business category.trader
as_of_dateYesCivil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.
quarter_turnoverYesQuarterly aggregate turnover in INR (₹).
preceding_fy_turnoverYesAggregate turnover of the preceding financial year in INR, as a string with exactly 2 decimal places. Required to check the Section 10 threshold.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / as_of_date
      Added value: +{
+  "description": "Civil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.",
+  "example": "2026-09-26",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "quarter_turnover",
-  "preceding_fy_turnover"
-]New value: +[
+  "quarter_turnover",
+  "preceding_fy_turnover",
+  "as_of_date"
+]
  2. Changed5 schema fields changed
    • addedInput schema / properties / preceding_fy_turnover
      Added value: +{
+  "description": "Aggregate turnover of the preceding financial year in INR, as a string with exactly 2 decimal places. Required to check the Section 10 threshold.",
+  "example": "12000000.00",
+  "pattern": "^\\d+\\.\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / quarter_turnover / example
      Added value: +"250000.00"
    • addedInput schema / properties / quarter_turnover / pattern
      Added value: +"^\\d+\\.\\d{2}$"
    • changedInput schema / properties / quarter_turnover / type
      Previous value: -"number"New value: +"string"
    • changedInput schema / required
      Previous value: -[
-  "quarter_turnover"
-]New value: +[
+  "quarter_turnover",
+  "preceding_fy_turnover"
+]
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description consistently supports that by saying the tool 'calculates' and 'computes' rather than mutating anything. It adds beyond the annotations by disclosing the rate schedule and that it 'enforces statutory turnover thresholds,' which tells an agent the tool will apply eligibility limits during calculation. The only omission is the precise failure mode when a threshold is exceeded.

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

Conciseness5/5

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

Two compact sentences front-load the core action and resource, then pack the differentiating category rates and threshold behavior into the second sentence. There is no filler or repetition of the title.

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 calculation-only tool with no output schema, the description makes the output concept ('quarterly tax liabilities') clear and covers the input categories and thresholds that determine the computation. It would be slightly more complete if it described the output shape (e.g., total liability or per-category breakdown), but the core invocation contract is present.

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 baseline is adequate, but the description adds extra meaning by mapping category values to concrete rates (trader/manufacturer 1%, restaurant 5%) and by clarifying that turnover parameters feed statutory threshold enforcement. It does not fully spell out how 'as_of_date' behaves beyond the schema's rule-pack note, but the added mapping is genuinely useful.

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?

The description opens with a specific verb ('Calculate') and a well-defined resource ('statutory GST quarterly tax liabilities under the Composition Scheme'), and immediately distinguishes itself from the sibling 'gst_regular' by naming Section 10 of the CGST Act. It also names the three supported categories and their rates, so an agent cannot mistake it for a generic GST tool.

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 phrase 'under the Composition Scheme (Section 10 of CGST Act)' provides clear context for when this tool is appropriate, and the turnover-threshold mention signals the main eligibility constraint. It does not explicitly name 'gst_regular' as the alternative or state when not to use it, so it stops short of a 5.

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

All TrueCalci toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources