gst-india-mcp

Get ITC ledger

get_itc_ledger

Fetch Input Tax Credit (ITC) ledger transactions within a specified date range. Requires an active taxpayer session to execute.

Instructions

Fetch the electronic Input Tax Credit (ITC) ledger transactions for a date range. Requires an active taxpayer session.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_itc_ledger"
  }
}

Input Schema

Name	Required	Description	Default
`to`	Yes	To date, DD/MM/YYYY
`from`	Yes	From date, DD/MM/YYYY

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the authentication requirement ('active taxpayer session') and implies a read-only fetch, but does not address response format, pagination, date handling, or failure modes. Gives partial transparency.

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?

Two short sentences, with the primary purpose first and the prerequisite second. No filler or repetition.

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

Completeness3/5

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

For a simple two-parameter, read-only tool, the purpose and prerequisite are present, but without an output schema or annotations, the description leaves response shape and error behavior unstated. Adequate for basic invocation, incomplete for robust agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers 100% of parameters with format descriptions, so the baseline is 3. The description adds only 'for a date range' without clarifying inclusivity, timezone, or ordering, so it provides no additional semantic weight.

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?

States a specific action ('Fetch') on a specific resource ('electronic Input Tax Credit (ITC) ledger transactions') with a date range. The resource type inherently differentiates it from sibling tools like get_cash_ledger and get_ledger_balance.

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

Usage Guidelines2/5

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

Only provides a prerequisite ('Requires an active taxpayer session') but no guidance on when to use this tool versus alternatives such as get_cash_ledger or get_ledger_balance. There are no explicit usage conditions or exclusions, so an agent must infer which ledger tool fits.

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

Deploy Server