Skip to main content
Glama
gst-tax-mcp

gst-tax-mcp

by zoeb-nomi

itr_turnover_reconcile_tool

Reconcile GSTR-3B annual turnover against ITR gross receipts to flag variances beyond 5% and presumptive-scheme limit breaches for tax review.

Instructions

ITR crossover: reconcile GSTR-3B annual turnover against the ITR gross receipts; flags variance beyond 5% and presumptive-limit breaches.

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": {
      "gstr3b_turnover": "<gstr3b_turnover>",
      "itr_gross_receipts": "<itr_gross_receipts>"
    },
    "name": "itr_turnover_reconcile_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
gstr3b_turnoverYes
itr_gross_receiptsYes
itr_presumptive_schemeNonone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose real behavior beyond the schema — a 5% variance threshold and presumptive-limit breach flagging — but it omits whether the call is purely computational/read-only, what the flagged output looks like, and whether any other thresholds apply.

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?

A single front-loaded sentence with a colon introducing the two compared figures and a semicolon introducing the flagging behavior. Dense and waste-free; only the clipped 'ITR crossover' opener costs a little clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with no annotations and no output schema, the description covers the purpose and the flagging logic but leaves the third parameter and the shape of the result unexplained. An agent could invoke it, but would be guessing on the presumptive-scheme input.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and only partly does. It clarifies the meaning of the two required numeric inputs by pairing them with GSTR-3B and ITR respectively, but says nothing about 'itr_presumptive_scheme' — its valid values, what 'none' means, or how it changes the presumptive-limit check it hints at.

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 names a specific verb ('reconcile') and two specific resources ('GSTR-3B annual turnover' vs 'ITR gross receipts'), which is enough to separate it from siblings like reconcile_itc_tool (ITC) or gstr1_summary_tool. It never names an alternative explicitly, 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 Guidelines3/5

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

Usage is only implied: an agent can infer you call this when you hold both a GSTR-3B turnover figure and an ITR gross-receipts figure and want a variance check. There is no statement of prerequisites, exclusions, or which sibling to use when the question is about input tax credit rather than turnover.

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