GST Insights API MCP Server

get_gst_details_using_company_name

Look up GST details by providing a company name. Obtain registration status, business address, and taxpayer information.

Instructions

Endpoint: /getGSTDetailsUsingCompanyName/:companyName Method: GET Description: Fetches GST details using the provided company name. Parameters: companyName (string, required): The name of the company. Responses: 200 OK: Returns GST details along with a timestamp. 400 Bad Request: Invalid company name. 500 Internal Server Error: An error occurred on the server. Example Request: GET /getGSTDetailsUsingCompanyName/jio

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Example value: Reliance Jio Infocomm Limited

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 5, 2026

TDQS

C2.7/5.0

Behavior3/5

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

No annotations present, so the description carries the burden. It discloses that the HTTP method is GET (implying read-only) and lists possible response codes (200, 400, 500) with an example. However, it does not explicitly state that the operation is non-destructive or mention authentication or rate limits.

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?

The description is well-structured with sections for endpoint, method, parameters, responses, and example. Each sentence is relevant, though it could be more concise by omitting the full endpoint path which duplicates the tool name.

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

Completeness2/5

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

With no output schema, the description only vaguely mentions 'Returns GST details along with a timestamp' without specifying the actual fields or format. The parameter name discrepancy undermines completeness, and error responses are listed but not detailed for each code.

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?

While the description adds a human-readable explanation ('The name of the company') and an example request, it mistakenly uses 'companyName' instead of the schema's required parameter 'name'. This contradiction outweighs the added value, as the agent may send the wrong key.

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 clearly states that it fetches GST details using the company name, differentiating it from siblings like get_gst_details_using_gst_number. However, the parameter name mismatch between the description (companyName) and the schema (name) casts doubt on whether the agent will invoke it correctly, slightly reducing clarity.

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

Usage Guidelines1/5

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

No usage guidelines provided; the description does not specify when to use this tool over siblings or mention any prerequisites. Worse, it gives an incorrect parameter name (companyName instead of the schema's name), which is misleading and could cause invocation failures.

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

Deploy Server