Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_presumptive_tax

Read-onlyIdempotent

Calculate presumptive income and tax for small businesses (44AD) or professionals (44ADA) from gross receipts, digital share, regime, age, and 80C deductions.

Instructions

Calculate tax under presumptive scheme (Sections 44AD, 44ADA).

Use when computing tax for small businesses or professionals under presumptive taxation.

Args: scheme: "44AD" or "44ADA" gross_receipts: Total gross receipts digital_receipt_percent: % of receipts via digital mode regime: "new" or "old" age: Assessee age deductions_80c: Section 80C deductions (old regime)

Returns: Presumptive income and total tax payable.

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": {
      "scheme": "<scheme>",
      "gross_receipts": "<gross_receipts>"
    },
    "name": "calculate_presumptive_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAssessee age
regimeNo'new' or 'old' tax regimenew
schemeYes'44AD' for business or '44ADA' for professionals
deductions_80cNoSection 80C deductions (old regime)
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
gross_receiptsYesTotal gross receipts in INR
digital_receipt_percentNoPercentage via digital mode

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / financial_year
      Added value: +{
      +  "default": "2025-26",
      +  "description": "Financial year (e.g. '2025-26', '2026-27')",
      +  "title": "Financial Year",
      +  "type": "string"
      +}
  2. Changed9 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / age / title
      Added value: +"Age"
    • addedInput schema / properties / deductions_80c / title
      Added value: +"Deductions 80C"
    • addedInput schema / properties / digital_receipt_percent / title
      Added value: +"Digital Receipt Percent"
    • addedInput schema / properties / gross_receipts / title
      Added value: +"Gross Receipts"
    • addedInput schema / properties / regime / title
      Added value: +"Regime"
    • addedInput schema / properties / scheme / title
      Added value: +"Scheme"
    • addedInput schema / title
      Added value: +"calculate_presumptive_taxArguments"
    • addedOutput schema / title
      Added value: +"calculate_presumptive_taxDictOutput"
  3. Addedv0.4.2

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds only that it returns presumptive income and total tax payable, and says nothing about the deemed-profit rates (8%/6% under 44AD, 50% under 44ADA), turnover ceilings, or how digital receipt percentage alters the outcome — the substantive behavior a caller would want to know.

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 purpose and usage guidance are front-loaded in two short sentences, followed by a scannable argument list. Slight waste in re-listing arguments already fully described in the schema, and the list is incomplete relative to the schema.

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?

With an output schema present, the description needn't detail return shape, and it still names the key outputs. For a 7-parameter domain calculation it covers the essentials, though it omits the statutory thresholds and rate mechanics that materially affect the answer.

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?

Schema description coverage is 100%, so the baseline is 3. The Args block largely restates the schema (scheme, gross_receipts, regime, age, deductions_80c) and adds no format rules, and it omits the financial_year parameter that exists in the schema, leaving that one undocumented in the prose.

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 verb and resource ('Calculate tax under presumptive scheme') and names the exact statutory schemes (Sections 44AD, 44ADA). This clearly separates it from the sibling calculate_income_tax, since an agent can tell presumptive computation from regular computation without opening a schema.

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?

'Use when computing tax for small businesses or professionals under presumptive taxation' gives a clear positive trigger tied to the eligible taxpayer type. It stops short of stating when NOT to use it (e.g., use calculate_income_tax for regular business income or when turnover exceeds presumptive thresholds).

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

Deploy Server

Other Tools