Skip to main content
Glama

CTC to monthly in-hand salary (India)

salary_in_hand
Read-onlyIdempotent

Estimate monthly take-home pay from yearly CTC after PF, professional tax and income tax (new or old regime).

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": {
      "ctc": "<ctc>"
    },
    "name": "salary_in_hand"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctcYesYearly CTC in rupees.
stateNoState for professional tax, e.g. Maharashtra.
pfModeNo
regimeNo
basicPctNoBasic as % of CTC (default 50).

Output Schema

NameRequiredDescriptionDefault
ctcYes
noteNo
toolNo
basicNo
gratuityNo
incomeTaxNo
employeePfNo
employerPfNo
grossSalaryNo
yearlyInHandYes
monthlyInHandYes
professionalTaxNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety behavior is covered. The description adds that the figure is an estimate and lists the deduction components, but it omits the assumptions that drive the number (financial year, standard deduction, how PF is capped), which are the details that would let an agent judge the output's reliability.

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?

A single sentence with the input, output, and deduction breakdown front-loaded; there is no filler and nothing an agent must read past to understand the core operation.

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?

An output schema exists, so return values need no explanation, and the description covers the main computation logic including the optional regime. The main residual gap is the absence of any assumption or limitation statement for a financial estimate tool with five parameters and region-specific tax rules.

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 60%; the two undocumented parameters are pfMode and regime, whose enums are largely self-explanatory. The description does implicitly illuminate the 'regime' parameter by naming new/old tax regimes and reinforces that PF is a factor, but it adds no detail on pfMode's capped/full/none semantics beyond what the enum already conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and transformation: 'Estimate monthly take-home pay from yearly CTC' after naming the exact deductions (PF, professional tax, income tax). This clearly separates it from siblings like calculate_gst or compare_tax_regimes, though it never names an alternative tool explicitly.

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 implied by the 'yearly CTC' and 'new or old regime' framing, which signals an India salaried-income context. However, there is no explicit statement of when to choose this tool versus compare_tax_regimes, which sits in the same problem space and could plausibly be confused with it.

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