Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

Salary calculator

salary_calculator
Read-onlyIdempotent

India pay calculators. mode 'ctc_to_in_hand' (needs annualCtc in INR) estimates monthly take-home with PF, gratuity and tax. mode 'hike' (needs currentSalary plus newSalary or hikePercent) shows the raise, real raise after inflation.

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": {
      "mode": "<mode>"
    },
    "name": "salary_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesCalculator.
annualCtcNoAnnual CTC in INR.
newSalaryNoNew salary.
hikePercentNoHike %.
basicPercentNoBasic pay as % of CTC (default 40).
currentSalaryNoCurrent salary.
inflationPercentNoInflation % for real-terms raise.
variablePayPercentNoVariable pay % of CTC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description only needs to add computation context. It does add that the CTC result is a monthly take-home decomposition (PF, gratuity, tax) and that the hike mode reports real terms after inflation, which helps an agent interpret results. It does not say anything about rounding, currency assumptions beyond INR, or how optional inputs alter the estimate, so it earns a 3 rather than more.

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?

Two sentences, front-loaded with the domain, then each mode with its prerequisites and its output in one clause. Nearly every phrase carries information. The one weakness is the clipped fragment style ("India pay calculators.") and the missing article/verb structure, which costs a bit of polish but not comprehension.

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 an 8-parameter, two-mode tool with no output schema, the description covers mode selection, required inputs, the currency unit, and what each mode returns in enough detail to call it correctly. Optional knobs like basicPercent and variablePayPercent are left to the schema, which documents them, and the absence of an output schema means return shape is partly inferred. An agent has what it needs, with minor gaps in interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 is the baseline, but the description goes beyond per-parameter definitions by stating cross-parameter requirements the schema cannot express: which parameter each mode consumes and that newSalary and hikePercent are alternatives for the hike mode. It does not explain how basicPercent, variablePayPercent or inflationPercent change the output, leaving some ambiguity. The conditional-requirement information is genuine added value above the schema.

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 opens with a specific domain ("India pay calculators") and then defines both operations concretely: 'ctc_to_in_hand' estimates monthly take-home including PF, gratuity and tax, while 'hike' computes a raise and the real raise after inflation. That is a clear verb+resource statement an agent can act on. It stops short of differentiating itself from look-alike siblings such as salary_analysis, salary_research or analyze_offer, so it is not a 5.

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?

Mode selection is made explicit by attaching the required inputs to each mode: 'ctc_to_in_hand' needs annualCtc, and 'hike' needs currentSalary plus either newSalary or hikePercent. That gives an agent a concrete rule for choosing a path. There is no when-not-to-use guidance and no routing to the analysis/research siblings that could plausibly cover adjacent needs.

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.