TeamPredict HR Calculators

Cost of a bad hire

cost_of_a_bad_hire

Read-onlyIdempotent

Estimate the total cost of one bad hire: the salary paid for lost productivity plus recruiting, onboarding, manager time, severance and the cost of hiring a replacement. Use it for a single failed hire with a known salary and tenure. Use employee_turnover_cost instead for the company-wide cost of turnover across many employees, and severance_pay for the pay owed to a departing employee. Every cost line is optional and defaults to the TeamPredict calculator's default; set a line to 0 to leave it out.

Input Schema

Name	Required	Description
`months_employed`	Yes	Months the hire stayed before leaving or being let go, 0 to 120.
`rehire_cost_usd`	No	Cost of finding and hiring the replacement, in US dollars. Default 8000.
`annual_salary_usd`	Yes	Annual salary of the role, in US dollars.
`onboarding_cost_usd`	No	Onboarding and training cost, in US dollars. Default 3000.
`recruiting_cost_usd`	No	Recruiting and agency cost, in US dollars. Default 5000.
`manager_time_cost_usd`	No	Value of manager and team time spent on the hire, in US dollars. Default 4000.
`lost_productivity_percent`	No	Share of the salary paid during the tenure that bought no useful work, 0 to 100. Default 60.
`severance_and_exit_cost_usd`	No	Severance and exit cost, in US dollars. Default 5000.

Output Schema

Name	Required	Description
`inputs`	Yes	The inputs as used, with defaults filled in.
`results`	Yes	The computed numbers. Unavailable numbers are null.
`summary`	Yes	One or two plain sentences with the headline numbers.
`calculator_url`	Yes	The TeamPredict calculator page that shows the same calculation, where a person can change the inputs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to cover safety. It adds useful behavioral context by explaining that every cost line is optional, defaults to the calculator's default, and can be excluded by setting it to 0.

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?

Front-loads the core purpose, then gives usage boundaries and alternatives in two compact sentences. The cost component list and default handling are useful and earn their place without excess.

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 output schema exists, return values need not be described. For an 8-parameter estimation tool, the description covers purpose, scope, alternatives, and optional parameter handling well enough for correct 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 description coverage is 100%, so the schema already documents each parameter and its default. The description adds practical semantics beyond the schema: cost lines are optional and setting one to 0 omits that line from the estimate.

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?

States a specific verb and resource: estimating the total cost of one bad hire, and lists the cost components included. It explicitly distinguishes itself from employee_turnover_cost and severance_pay, so an agent can select it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: a single failed hire with known salary and tenure. It also names two sibling tools and explains when to use them instead, covering both the primary use case and the main alternatives.

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

All TeamPredict HR Calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?