eco-policy-mcp

Gst Reverse Charge

gst_reverse_charge

Calculate GST payable under the reverse charge mechanism for a taxable amount and slab rate, returning tax liability under Section 9(3)/9(4).

Instructions

Compute tax payable under reverse charge mechanism (Section 9(3)/9(4)).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`amount`	Yes	Taxable base amount in INR.
`rate_percent`	Yes	GST slab rate - one of 0.25, 3, 5, 12, 18, 28.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the legal basis for the calculation, which adds useful context, but does not describe rounding, treatment of the base amount, or other behavioral details beyond the basic operation.

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?

A single, tightly worded sentence that front-loads the core purpose. No wasted words or unnecessary repetition.

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?

Given the low complexity, full schema coverage, and the presence of an output schema, the description is nearly complete for calling the tool correctly. The only gap is the lack of usage guidance relative to sibling GST tools.

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 both parameters are already documented in the input schema. The description adds no further meaning about 'amount' or 'rate_percent' beyond what the schema provides, making the baseline score of 3 appropriate.

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 computational verb ('Compute') and a precise resource ('tax payable under reverse charge mechanism'), with legal section references that distinguish it from sibling GST calculators like gst_split and gst_from_inclusive.

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

Usage Guidelines2/5

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

No explicit when-to-use, when-not-to-use, or alternative guidance is given. The description does not mention sibling tools or conditions that select this tool over other GST calculators, leaving usage entirely implied by the tool name.

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

Deploy Server