India Invoices (GST e-invoicing IRN via IRP)
Server Details
India GST e-invoicing for AI agents - generate, query, cancel IRNs at the IRP via a GSP. Stateless.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 3 of 3 tools scored.
Each tool targets a distinct operation: create, cancel, and query invoices. There is no overlap in functionality, and descriptions clearly differentiate their purposes.
All tools follow a consistent verb_noun pattern with snake_case (cancel_invoice, create_invoice, query_invoice), making naming predictable and easy to understand.
Three tools cover the essential operations for e-invoicing (create, cancel, query) without unnecessary extras. The count is well-scoped for the server's purpose.
The server covers the main lifecycle: creation, cancellation (within 24h), and querying. However, there is no tool for credit notes or post-24h corrections, which are noted as necessary but missing, creating a minor gap.
Available Tools
3 toolscancel_invoiceADestructiveIdempotentInspect
Cancel a GST e-invoice at the IRP. IMPORTANT: the IRP only allows cancellation WITHIN 24 HOURS of IRN generation (and only if no e-way bill is active / it was not already cancelled) — after 24h you must instead issue a credit note. A reason code is required: 1 Duplicate, 2 Data entry mistake, 3 Order cancelled, 4 Others (default 4). Remarks are required by the IRP.
| Name | Required | Description | Default |
|---|---|---|---|
| irn | Yes | The IRN returned by create_invoice. | |
| remarks | No | Free-text remarks explaining the cancellation (required by the IRP), max 100 chars. | |
| reason_code | No | NIC cancellation reason: 1 Duplicate, 2 Data entry mistake, 3 Order cancelled, 4 Others. Default 4. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds critical behavioral details beyond annotations: 24-hour window, required reason code and remarks, alternative of credit note. Annotations only say destructive and idempotent hints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Concise and front-loaded, but uses all-caps emphasis and could be slightly more streamlined. No wasted sentences.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers key constraints but does not mention response format or error handling, which would be helpful for a cancellation tool with no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters. Description adds extra context: reason code meanings and that remarks are required by IRP, enhancing agent understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses specific verb 'Cancel' and resource 'GST e-invoice at the IRP', clearly distinguishing from siblings create and query.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use (within 24 hours of IRN generation) and when not (after 24 hours must issue credit note), plus prerequisites (no e-way bill active, not already cancelled).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
create_invoiceAInspect
Generate a GST e-invoice and get an IRN (Invoice Reference Number) from the IRP (Invoice Registration Portal, run by GSTN), stamped through the Sandbox.co.in GSP. Bring your own Sandbox credentials via headers x-sandbox-api-key AND x-sandbox-api-secret (sign up at sandbox.co.in). Your GSTIN must already have GST e-Invoice API access enabled on the e-Invoice portal and mapped to Sandbox as your GSP. e-Invoicing is B2B only — BOTH seller and buyer must have valid 15-char GSTINs. Give flat fields (seller/buyer GSTIN + name + address, doc_number, line items with hsn_code, price, quantity, gst_rate) and this server COMPUTES the INV-01 tax schema for you: taxable value per line, CGST+SGST split for same-state supply vs IGST for cross-state supply (decided automatically from the seller GSTIN state vs the place-of-supply state), item totals, and the invoice totals (AssVal / TotInvVal). Returns Irn, AckNo, AckDt and SignedQRCode.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Line items. Each: description, hsn_code (HSN/SAC), price (unit price in INR, tax-EXCLUSIVE), gst_rate (percent, e.g. 18), optional quantity (default 1) and unit (default NOS). GST is computed on top of price*quantity. | |
| doc_date | No | Invoice date DD/MM/YYYY (DocDtls.Dt). Defaults to today (UTC). | |
| buyer_city | Yes | Buyer city / location (Loc). | |
| doc_number | Yes | Your invoice/document number (DocDtls.No), max 16 chars. | |
| buyer_gstin | Yes | Buyer (recipient) 15-char GSTIN. Required — e-invoicing is B2B only. | |
| seller_city | Yes | Seller city / location (Loc). | |
| seller_gstin | Yes | Seller (supplier) 15-char GSTIN, e.g. 29ABCDE1234F1Z5. Its first 2 digits are the seller state code and drive the CGST+SGST vs IGST decision. | |
| buyer_address | Yes | Buyer address line 1 (Addr1). | |
| buyer_pincode | Yes | Buyer 6-digit PIN code (Pin). | |
| seller_address | Yes | Seller registered address line 1 (Addr1). | |
| seller_pincode | Yes | Seller 6-digit PIN code (Pin). | |
| buyer_legal_name | Yes | Buyer legal name (LglNm) as registered under the buyer GSTIN. | |
| buyer_state_code | No | Optional place-of-supply state code (POS), 2 digits. Defaults to the buyer GSTIN state code. Set this if the place of supply differs from the buyer registration state. | |
| seller_legal_name | Yes | Seller legal name (LglNm) exactly as registered under this GSTIN. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description complements annotations (readOnlyHint=false, destructiveHint=false) by detailing the creation process, tax computation, authentication headers, and return values. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is relatively long but well-structured and front-loaded with the core purpose. Every sentence adds value, though could be slightly more concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having no output schema, the description fully covers authentication, prerequisites, tax computation, return fields (Irn, AckNo, AckDt, SignedQRCode), and parameter details, making it complete for a complex tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds significant meaning beyond schema: explains tax split based on GSTIN state, default values, and purpose of each parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'Generate a GST e-invoice and get an IRN' and details the entire process, clearly distinguishing from sibling tools (cancel_invoice, query_invoice) which handle cancellation and querying.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit context: B2B only, requires credentials, GSTIN must have e-Invoice API access. It does not explicitly state when not to use or alternatives, but the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
query_invoiceARead-onlyInspect
Look up a GST e-invoice by its IRN at the IRP. Status values: ACT (active / valid) or CNL (cancelled). Safe to call anytime.
| Name | Required | Description | Default |
|---|---|---|---|
| irn | Yes | The 64-char IRN returned by create_invoice. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint; description adds specific status values (ACT, CNL) and reaffirms safety, adding value beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words, essential information front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Simple tool with one parameter and no output schema; description provides purpose, status values, and safety. Could mention typical response fields but not necessary for this level of complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema's parameter description already includes the key detail '64-char IRN returned by create_invoice'; description adds no further semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clear verb 'Look up' and resource 'GST e-invoice by its IRN at the IRP', explicitly distinguishing from sibling tools cancel_invoice and create_invoice.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
States 'Safe to call anytime' which implies unrestricted usage, but does not explicitly contrast with when to use cancel_invoice or create_invoice; still clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!