Skip to main content
Glama

Business Calculator: GST, Margin & Everyday Formulas

HR, Payroll & Gratuity Calculators — Saifs AI

hr_payroll_calculators
Read-only

Calculate payroll, gratuity and workforce metrics exactly: overtime pay, pro-rata salary for joiners and leavers, leave accrual (OSH Code 1 day per 20 worked), gratuity (15/26, ₹20 lakh cap, 5-year rule, fixed-term 1 year under the Code on Social Security from 21-Nov-2025); attrition, average headcount, absenteeism, cost per hire, revenue per employee, billable utilisation. Returns a standard-library Python script with only these calculators (payroll_calculator, workforce_metrics_calculator) to run in your code sandbox; each answer gives result, formula, inputs used, rounding, rule version and effective date. Inputs: tools (narrow to some of these calculators), calls ([{tool, operation, inputs, rounding?, as_of?}] baked into the script; a calculator from another area named in calls is added), calls_path (JSON file of calls in your sandbox). Calculation never runs on this server or any API. Not for EMI / interest / NPV / IRR (refused), nor salary income-tax, PF / ESI contributions, legal advice. Operation and input names: business_calculator_list_formulas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hr_payroll_calculators"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsNoCalculations to bake into the script (their calculators are included).
toolsNoNarrow the script to some of this area's calculators (default: all of them).
calls_pathNoJSON file of calls already in your sandbox.
full_catalogNoKeep descriptions and worked examples inside the script (larger).

Output Schema

NameRequiredDescriptionDefault
areaNo
notesNo
scriptYes
languageNo
requiresNo
calls_pathNo
operationsNo
call_formatNo
instructionsYes
writes_filesNo
calls_baked_inNo
engine_versionYes
included_toolsYes
server_computesNo
network_access_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the key execution model: the tool returns a standard-library Python script to run in the caller's sandbox, and calculation never runs on this server or any API. It also explains that each answer includes result, formula, inputs used, rounding, rule version, and effective date, which is substantial behavioral context.

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 description front-loads the core purpose and covered metrics, then moves through output behavior, inputs, exclusions, and formula-reference guidance. It is dense and somewhat run-on, but the rule details such as 15/26, the ₹20 lakh cap, and the 5-year rule are relevant to scoping the calculators rather than filler.

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?

Given the four-parameter schema, full schema description coverage, annotations, and an output schema, the description supplies everything an agent needs: what is calculated, what is excluded, how the script is produced and run, and how to look up operation and input names. No material gap remains for correct tool selection or invocation.

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 the baseline is 3, but the description adds meaning for tools (narrow the script to selected calculators), calls (baked into the generated script, with cross-area calculators added), and calls_path (JSON file already in the sandbox). It does not explain full_catalog in the description, but that parameter is fully documented in the schema.

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 and resource: calculate payroll, gratuity, and workforce metrics, then enumerates the exact metrics covered. It also explicitly excludes EMI/interest/NPV/IRR, salary income-tax, PF/ESI, and legal advice, which helps an agent distinguish this tool from finance-oriented siblings.

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?

The description clearly indicates when to use the tool (payroll, gratuity, and workforce metric calculations) and when not to use it (EMI/interest/NPV/IRR, salary income-tax, PF/ESI, legal advice). It stops short of naming a specific alternative sibling for the excluded domains, so it is strong but not fully explicit on alternatives.

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.