Fast GST Refund

List the fields of Annexure B JSON

get_annexure_b_requirements

Read-onlyIdempotent

Returns the fields of the Annexure B JSON (statement of inward-supply invoices) for a GST refund of accumulated ITC (RFD-01), the file the GST portal otherwise requires from its Excel offline utility, and where each value comes from: purchase documents, tax amounts, the GSTR-2B period, reviewed ITC eligibility and the eight GSTR-3B reversal totals, with the fields each supply type leaves empty. Takes no input. Use it before validate_annexure_b to learn which fields to collect.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`scope`	No
`checks`	No
`limits`	No
`sha256`	No
`sources`	Yes
`utility`	No
`accepted`	No
`document`	Yes
`workflow`	Yes
`references`	No
`inputSchema`	Yes
`jsonVersion`	No
`notIncluded`	No
`utilityVersion`	No
`generatorVersion`	No
`fieldRulesBySupplyType`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 6, 2026

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -{}New value: +true
```

addedOutput schema / properties

Added value: +{
+  "accepted": {
+    "additionalProperties": true,
+    "properties": {
+      "amounts": {
+        "type": "string"
+      },
+      "dates": {
+        "type": "string"
+      },
+      "existingFiles": {
+        "type": "string"
+      },
+      "periods": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "checks": {
+    "type": "string"
+  },
+  "document": {
+    "type": "string"
+  },
+  "fieldRulesBySupplyType": {
+    "additionalProperties": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "object"
+  },
+  "generatorVersion": {
+    "type": "string"
+  },
+  "inputSchema": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "jsonVersion": {
+    "type": "string"
+  },
+  "limits": {
+    "additionalProperties": true,
+    "properties": {
+      "requestBytes": {
+        "type": "number"
+      },
+      "rowsPerFile": {
+        "type": "number"
+      },
+      "splitUploads": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "notIncluded": {
+    "type": "string"
+  },
+  "references": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "scope": {
+    "type": "string"
+  },
+  "sha256": {
+    "type": "string"
+  },
+  "sources": {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "fields": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "fields",
+        "source"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "utility": {
+    "type": "string"
+  },
+  "utilityVersion": {
+    "type": "string"
+  },
+  "workflow": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}

removedOutput schema / propertyNames

Removed value: -{
-  "type": "string"
-}

addedOutput schema / required

Added value: +[
+  "document",
+  "workflow",
+  "sources",
+  "inputSchema"
+]

AddedOct 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that: the source of each value (purchase documents, tax amounts, GSTR-2B period, reviewed ITC eligibility, eight GSTR-3B reversal totals) and the fact that certain fields are left empty per supply type.

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?

Front-loaded with the resource identity, followed by value-origin detail and then the routing instruction. The middle sentence is dense and long, but every clause carries substantive information about the returned fields rather than filler.

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?

An output schema exists, so return values need not be enumerated in prose; the description instead adds domain framing and workflow ordering, which is exactly the right complement. It is complete enough to call the tool correctly, though the pre-validation step could have named its other sibling (generate_annexure_b) for full routing coverage.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description's explicit 'Takes no input' correctly reinforces the empty schema.

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?

Names a specific verb and resource ('Returns the fields of the Annexure B JSON') and pins down the domain context (inward-supply statement for an RFD-01 ITC refund). It is clearly distinguishable from the sibling generate_annexure_b and validate_annexure_b tools, which produce and check the same artifact.

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?

Explicitly routes the agent: 'Use it before validate_annexure_b to learn which fields to collect.' It also states 'Takes no input', removing any ambiguity about invocation. Both when-to-use and its relative ordering in the workflow are given.

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

All Fast GST Refund tools Inspect

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.