PaycheckHours calculators

Overtime pay

overtime_pay

Regular, overtime and double-time pay from an hourly rate and hours. Overtime multiplier defaults to 1.5 (US federal minimum for covered, non-exempt work over 40 hours a week); double time is 2x.

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": {
      "hourly_rate": "<hourly_rate>",
      "regular_hours": "<regular_hours>",
      "overtime_hours": "<overtime_hours>"
    },
    "name": "overtime_pay"
  }
}

Input Schema

Name	Required	Description	Default
`hourly_rate`	Yes
`regular_hours`	Yes
`overtime_hours`	Yes
`double_time_hours`	No
`overtime_multiplier`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses defaults the schema does not (multiplier 1.5, double time 2x) and grounds them in the US federal rule, but says nothing about permissions, limits, or whether the result is a total or a breakdown.

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?

Two tightly written sentences: the core computation first, then the multiplier semantics. No filler, and the most decision-relevant detail (the default) is surfaced immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No annotations and no output schema mean the description is the only source of truth, yet it never says what the return value looks like (a single number, a component breakdown, currency formatting). For a five-parameter calculation tool this leaves a meaningful gap.

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?

At 0% schema coverage the description has to explain all five parameters, and it effectively does: hourly rate and hours of each category are implied, double_time_hours is defined as 2x, and overtime_multiplier gets a default value of 1.5 with rationale. It stops short of defining boundaries such as whether regular_hours is capped at 40.

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 names a specific computation ('regular, overtime and double-time pay from an hourly rate and hours'), so the agent knows exactly what the tool produces. It does not, however, differentiate itself from the sibling calculate_time_card, which likely overlaps in scope.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus calculate_time_card or any other sibling, nor any prerequisites or exclusions. Usage is only inferable from the names of the inputs, leaving the agent to guess between overlapping pay-calculation tools.

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

All PaycheckHours 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?