Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_professional_tax

Read-onlyIdempotent

Compute state-wise professional tax from monthly gross salary and state code, returning monthly and annual amounts for accurate tax liability.

Instructions

Calculate state-wise professional tax.

Use when computing total tax liability including professional tax deductions.

Args: gross_salary_monthly: Monthly gross salary state_code: 2-char state code (e.g., "MH", "KA", "TN")

Returns: Monthly and annual professional tax amount.

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": {
      "gross_salary_monthly": "<gross_salary_monthly>",
      "state_code": "<state_code>"
    },
    "name": "calculate_professional_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
state_codeYes2-char state code (e.g., MH, KA, TN)
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
gross_salary_monthlyYesMonthly gross salary in INR

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. Changed5 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / gross_salary_monthly / title
      Added value: +"Gross Salary Monthly"
    • addedInput schema / properties / state_code / title
      Added value: +"State Code"
    • addedInput schema / title
      Added value: +"calculate_professional_taxArguments"
    • addedOutput schema / title
      Added value: +"calculate_professional_taxDictOutput"
  3. Addedv0.4.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds that results are state-wise and reported both monthly and annually, but says nothing about unsupported state codes, invalid salary inputs, or how the defaulted financial_year affects results.

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 core sentence is front-loaded and efficient, but the Args and Returns blocks duplicate the input and output schemas almost word for word. It is well structured but carries redundancy that does not earn its place.

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 three-parameter, read-only calculation tool with full schema coverage and an output schema, the definition is largely sufficient — the return values are already structured. The remaining gap is edge-case behavior for invalid or unsupported inputs.

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 restates the schema verbatim and adds no new meaning, such as how state slabs vary, what happens with an unsupported state code, or how financial_year changes the computed rate.

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 names a specific verb and resource ('Calculate state-wise professional tax'), which clearly separates it from sibling calculators such as calculate_tds, calculate_gst, and calculate_income_tax. An agent can identify the operation without consulting the schema.

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?

It gives one implied usage cue ('Use when computing total tax liability including professional tax deductions'), which hints at context but does not specify when to prefer this tool over related calculators or what prerequisites exist. No exclusions or alternative routing are stated.

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