gst-india-mcp

Get GSTR-2B

get_gstr2b

Retrieve GSTR-2B auto-drafted purchase ITC statement for a specified return period (year and month) to reconcile input tax credit during GST filing.

Instructions

Fetch GSTR-2B (auto-drafted ITC statement of purchases) for a return period. Requires an active taxpayer session.

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": {
      "year": "<year>",
      "month": "<month>"
    },
    "name": "get_gstr2b"
  }
}

Input Schema

Name	Required	Description	Default
`year`	Yes	4-digit year, e.g. 2026
`month`	Yes	2-digit month, e.g. 09

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It notes the session requirement, which is a behavioral precondition, but does not mention whether the operation is read-only, potential side effects, or error behavior. Partial transparency at best.

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?

The description is exceptionally concise, consisting of two short sentences that convey the essential information without any redundant language or unnecessary detail.

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?

For a simple fetch operation with no output schema and no annotations, the description is complete. It states the purpose, the required parameters via the schema, and the session prerequisite, covering all necessary context for an agent to use the tool.

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?

The schema already provides descriptions and examples for both parameters (year and month), achieving 100% coverage. The description does not add additional meaning beyond what the schema states, so the baseline score of 3 applies.

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 clearly states the verb 'Fetch' and the resource 'GSTR-2B', along with the scope 'for a return period'. It accurately conveys the tool's function without ambiguity.

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?

The description mentions a prerequisite ('Requires an active taxpayer session') but does not provide explicit guidance on when to use this tool versus sibling tools like get_gstr3b or track_returns_current. The usage context is implied rather than clearly differentiated.

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

Deploy Server