GST Insights API MCP Server

get_gst_details_using_gst_number

Retrieve GST registration status, business address, and filing history by providing a valid GST number.

Instructions

Endpoint: /getGSTDetailsUsingGST/:gst Method: GET Description: Fetches GST details using the provided GST number. Parameters: gst (string, required): A valid GST number (15 characters). Responses: 200 OK: Returns GST details along with a timestamp. 400 Bad Request: Invalid GST number. 500 Internal Server Error: An error occurred on the server. Example Request: GET /getGSTDetailsUsingGST/22ABCDE1234F1Z5

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": {
      "gstNumber": "<gstNumber>"
    },
    "name": "get_gst_details_using_gst_number"
  }
}

Input Schema

Name	Required	Description	Default
`gstNumber`	Yes	Example value: 27AABCI6363G3ZH

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses the read-only nature (GET method), parameter format (15-character), and error responses (400, 500). However, lacks details on authentication or rate limits, but acceptable for a simple lookup.

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

Conciseness3/5

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

The description is a single paragraph with technical details (endpoint, method, responses) but is somewhat verbose and not tightly structured. Could be more concise while retaining all key information.

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 simple GET request with one parameter and no output schema, the description adequately covers purpose, input, and expected responses (200, 400, 500). Missing detailed response structure, but overall sufficient.

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 input schema only provides an example value with 100% coverage. The description adds meaningful context: 'A valid GST number (15 characters)' and an example request, clarifying the required format beyond the 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?

The description clearly states it fetches GST details using a GST number. The sibling tools (e.g., get_gst_details_using_company_name, get_gst_details_using_pan) differ in input, making this tool distinct and specific.

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?

Explicitly specifies the HTTP method, endpoint, required parameter, and response codes. Implicitly suggests usage when a GST number is available, but lacks explicit guidance on when not to use or alternatives.

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

Deploy Server