Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculate_professional_tax

Read-onlyIdempotent

Calculate professional tax amounts for any Indian state using monthly gross salary and state code, returning monthly and annual 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
state_codeYes2-char state code (e.g., MH, KA, TN)
gross_salary_monthlyYesMonthly gross salary in INR

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Addedv0.4.2

TDQS

A4.1/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 safety profile is covered. The description adds that the tool is state-wise and returns both monthly and annual amounts, which is useful but does not go much beyond the schema. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, front-loaded with the main purpose, and has a short usage line plus essential args and returns. No unnecessary filler or redundant detail beyond a reasonable reminder of the two key arguments.

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

Completeness5/5

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

For a simple calculation with two fully documented parameters, output schema present, and annotations covering read-only/idempotent behavior, the description is complete enough for an agent to select and invoke the tool correctly without further clarification.

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% and both parameters are already described with units and examples. The description repeats the parameter names without adding substantive semantic detail beyond what the schema provides, so a baseline score is appropriate.

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 opens with a specific verb and resource: 'Calculate state-wise professional tax.' This clearly identifies the tool's unique function among many sibling tax calculators like calculate_income_tax and calculate_tds, and the subject is not confused with any other calculation.

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?

It explicitly states when to use the tool: 'Use when computing total tax liability including professional tax deductions.' This gives a clear trigger context, though it does not mention alternatives or exclusions; still, it is sufficient to guide an agent toward this tool.

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