Skip to main content
Glama

BRAINIAC Global Employment Rules

Calculate US overtime pay

global-employment_us-overtime-calculate
Read-onlyIdempotent

Calculate federal FLSA weekly overtime, or California daily, seventh-day, and weekly overtime, from one caller-supplied workweek before you hire or engage a worker in a country. Call with jurisdiction, hourlyRateCents, and days. Returns regularHours, overtime15Hours, doubleTimeHours, regularPayCents, overtimePayCents, doubleTimePayCents, and totalCents. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: before you hire or engage a worker in a country, jurisdiction, hourlyRateCents, days, regularHours, overtime15Hours, doubleTimeHours, regularPayCents, overtimePayCents, doubleTimePayCents, totalCents, Calculate US overtime pay, us overtime calculate.

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": {
      "jurisdiction": "<jurisdiction>",
      "hourlyRateCents": "<hourlyRateCents>",
      "days": "<days>"
    },
    "name": "global-employment_us-overtime-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesdays, array. Required.
jurisdictionYesjurisdiction, string, one of federal, california. Required.
hourlyRateCentsYeshourlyRateCents, integer, from 0 to 1000000. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
totalCentsNototalCents. Number.
limitationsNolimitations. Array.
regularHoursNoregularHours. Number.
doubleTimeHoursNodoubleTimeHours. Number.
overtime15HoursNoovertime15Hours. Number.
regularPayCentsNoregularPayCents. Number.
overtimePayCentsNoovertimePayCents. Number.
doubleTimePayCentsNodoubleTimePayCents. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds important billing behavior: HTTP 200 responses with status complete, partial, or failed are charged at the full price, while 4xx/5xx responses are not charged. It also confirms the calculations and return fields, though some return detail overlaps with the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentences are useful and front-loaded, but the description then appends a long 'Keywords:' list that repeats the title, parameter names, return fields, and an awkward phrase about hiring in a country. This keyword stuffing does not help an agent select or invoke the tool, so the definition is noticeably less concise than it should be.

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 a calculation tool with an output schema, the description covers the calculation scope, required inputs, jurisdiction behavior, and billing outcomes. It is nearly complete, though it could better clarify what 'partial' status means in practice.

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 100%, so the schema already documents jurisdiction, hourlyRateCents, and the days array with date and hours. The description restates parameter names and says to supply one workweek, but adds little semantic meaning beyond 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 names the exact resource and calculation: federal FLSA weekly overtime versus California daily, seventh-day, and weekly overtime. It uses a specific verb (Calculate) and distinguishes the two supported jurisdictions, so an agent can immediately understand what the tool does.

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 gives a clear usage context: it should be used before hiring or engaging a worker, and it states to call with jurisdiction, hourlyRateCents, and days. It does not explicitly name when not to use it or point to sibling alternatives, but the pre-hire context is clear.

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