Skip to main content
Glama
gst-tax-mcp

gst-tax-mcp

by zoeb-nomi

gst_applicability

Determine if a business needs GST registration and whether it qualifies for the composition scheme from a JSON profile of turnover, state, supply type, and e-commerce activity.

Instructions

Does this business need GST registration, and is it eligible for the composition scheme? profile is a JSON object (or path to one): aggregate_turnover_prior_fy, state_code, supplies_goods, supplies_services, inter_state_supply, sells_via_ecommerce, casual_taxable_person, composition_scheme_interest.

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

Input Schema

NameRequiredDescriptionDefault
profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It identifies the two determinations and lists profile fields, but it does not state assumptions, thresholds, jurisdictional/version basis, output shape, or whether the result is advisory rather than definitive.

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 front-loaded with the core question and then compactly explains the profile parameter and its fields. It is appropriately sized for a single-parameter tool, with no filler or repetition.

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?

For a compliance determination tool with no annotations, no output schema, and 0% schema description coverage, the description gives input fields but not output structure, legal basis, assumptions, or limitations. It is enough to start constructing a profile but not complete enough to safely interpret the result.

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?

Schema coverage is 0%, and the schema only says profile is a string. The description substantially compensates by explaining that profile is a JSON object or path to one and by enumerating eight business-profile fields, though it still omits field types, allowed values, and requiredness for those nested fields.

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 states two specific determinations: whether GST registration is needed and whether the business is eligible for the composition scheme. It is clearly about GST applicability based on a business profile, but it does not explicitly differentiate itself from siblings such as calc_gst_liability or gst_filing_deadlines.

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?

Use is implied by the question 'Does this business need GST registration...' and the profile input, so an agent can infer the tool is for registration/composition applicability checks. However, there is no explicit when-to-use, when-not-to-use, prerequisite, or alternative-tool guidance.

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