Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculate_presumptive_tax

Read-onlyIdempotent

Calculate presumptive income and tax payable for small businesses or professionals under Sections 44AD or 44ADA using gross receipts, digital receipt percentage, tax regime, age, and 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoAssessee age
regimeNo'new' or 'old' tax regimenew
schemeYes'44AD' for business or '44ADA' for professionals
deductions_80cNoSection 80C deductions (old regime)
gross_receiptsYesTotal gross receipts in INR
digital_receipt_percentNoPercentage via digital mode

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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 and idempotentHint, so the description doesn't need to discuss destructive side effects. The description adds a basic return summary ('Presumptive income and total tax payable') but no deeper behavioral context such as calculation assumptions or edge-case handling; a neutral 3 is appropriate.

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 fairly concise and front-loads the core purpose before listing parameters. The Args block duplicates schema information, which is slightly redundant, but it is still readable and focused, earning it a 4 rather than a 5.

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?

For a tool with 6 parameters, 100% schema coverage, a rich annotation profile, and an output schema, the description is adequately complete. It conveys the main use case, the two schemes, and the expected return. It could add more nuance about how digital_receipt_percent or regime affects the calculation, but it is not incomplete enough to prevent correct tool invocation.

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?

The schema description coverage is 100%, so the baseline is 3. The narrative Args block mostly restates the schema's parameter descriptions without adding meaningful new semantics about how the parameters affect the calculation. It provides no extra insight beyond the schema.

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?

The description clearly states the verb 'calculate' and the resource: tax under the presumptive scheme, with explicit sections (44AD, 44ADA). This separates it from sibling tax calculators like calculate_income_tax or calculate_professional_tax.

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?

Explicit guidance is given: 'Use when computing tax for small businesses or professionals under presumptive taxation.' It does not explicitly name alternatives or when-not-to-use, so it is not a perfect 5, but the usage context is clear enough for an agent to select this tool appropriately.

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