Skip to main content
Glama

Salary in-hand from CTC

calculate_salary_in_hand
Read-onlyIdempotent

Monthly and yearly in-hand salary from an annual CTC in India under the new tax regime (FY 2026-27). Assumes employee and employer PF at 12% of basic capped at Rs 1,800 a month, gratuity at 4.81% of basic, and professional tax of Rs 200 a month. Variable pay is shown separately after its own tax.

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": {
      "annual_ctc": "<annual_ctc>"
    },
    "name": "calculate_salary_in_hand"
  }
}

Input Schema

NameRequiredDescriptionDefault
annual_ctcYesAnnual CTC in rupees
basic_percentNoBasic salary as % of fixed pay (default 50)
variable_pay_percentNoVariable pay or bonus as % of CTC (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, closed-world calculation, so the safety profile is covered. The description then adds the substantive behavioral context that annotations cannot: the exact statutory assumptions (12% PF capped at Rs 1,800/month, 4.81% gratuity, Rs 200 professional tax) and the fact that variable pay is taxed separately. What is missing is any note on how results are presented (output schema absent).

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?

Three sentences, front-loaded with purpose, then assumptions, then the variable-pay caveat; nothing is redundant. It is dense with numbers but every figure carries behavioral information, though a reader must parse a long second sentence to extract the assumption list.

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 deterministic calculator with annotations covering safety and no output schema, the description supplies the regime, fiscal year and all hard-coded statutory assumptions an agent needs to trust the result. The remaining gap is the shape of the returned figures (breakdown components, monthly vs yearly emphasis), which nothing else documents.

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 each of the three parameters is already documented with ranges and defaults. The description clarifies how variable pay is reported but does not explain the effect of basic_percent on the PF cap or the default of 50, so it adds only marginal meaning beyond the schema. Baseline 3 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 gives a specific verb+resource pair ('Monthly and yearly in-hand salary from an annual CTC') and pins scope with jurisdiction (India), regime (new tax regime) and fiscal year (FY 2026-27). That scoping implicitly separates it from the regime-comparison and tax-deduction siblings, so an agent can identify what it does without opening 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?

Usage is only implied: the tool applies to the new regime for FY 2026-27, which tells the agent when it fits but not when it does not. There is no explicit pointer to an alternative for the old regime or for regime comparison, and no statement about input prerequisites beyond the schema constraints.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources