Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_salary_to_hourly

Convert annual salary into equivalent hourly, weekly, and bi-weekly pay rates using standard 2,080 work hours to avoid manual wage calculation errors.

Instructions

Salary to Hourly Wage Calculator. Convert annual salary into equivalent hourly, daily, weekly, and bi-weekly wage rates based on standard 2,080 annual work hours. Discipline: FINANCE. Governing mathematical model / formula: Hourly Wage = Annual Salary / 2,080 Hours (40 hrs/wk × 52 weeks).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of hourly_rate (Equivalent Hourly Wage), weekly_rate (Weekly Pay), biweekly_rate (Bi-Weekly Paycheck) using annual_salary (Annual Salary ($)), hours_per_week (Work Hours per Week in hrs), paid_weeks (Paid Weeks per Year in wks). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Salary to Hourly Wage Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "salary-to-hourly"

    • category (string): "finance"

    • name (string): "Salary to Hourly Wage Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.hourly_rate (Equivalent Hourly Wage): Formatted display string (e.g. '$40.87 / hr')

      • metrics.weekly_rate (Weekly Pay): Formatted display string (e.g. '$1,634.62')

      • metrics.biweekly_rate (Bi-Weekly Paycheck): Formatted display string (e.g. '$3,269.23')

    • execution_time_ms (number): Latency in milliseconds.

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": "omni_salary_to_hourly"
  }
}

Input Schema

NameRequiredDescriptionDefault
paid_weeksNoPaid Weeks per Year (wks). 52 weeks including paid time off. Default: 52. Min: 40. Max: 52.
annual_salaryNoAnnual Salary ($). Base annual compensation. Default: 85000. Min: 10000. Max: 1000000.
hours_per_weekNoWork Hours per Week (hrs). Standard is 40 hours per week. Default: 40. Min: 10. Max: 80.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied, the description fully carries the behavioral burden by disclosing deterministic, read-only, idempotent, stateless operation with no side effects. It also explains bounds validation, diagnostic error responses for invalid inputs, floating-point computation, and formatted metric strings.

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

Conciseness3/5

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

The headings and front-loaded purpose make the long description easy to navigate, and the return documentation is useful because no output schema exists. Nevertheless, precision and determinism are repeated, and the overall length is substantial for a simple three-parameter calculator.

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?

The definition supplies nearly all invocation, safety, error-handling, and return-shape information needed in the absence of annotations and an output schema. However, it promises a daily rate that is absent from the documented metrics, and its fixed 2,080-hour formula leaves the effect of custom hours and paid weeks ambiguous.

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 coverage is 100%, including parameter meanings, defaults, and bounds, so the baseline is 3. The description adds the default 2,080-hour formula and maps parameters to calculated rates, but it does not explain how non-default hours_per_week and paid_weeks generalize that fixed formula.

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 clearly states that the tool converts an annual salary into hourly and other wage rates, identifies the finance domain, and provides the governing calculation. It also distinguishes this specialist from omni_universal_query, omni_batch_calculate, and omni_describe_solver.

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?

Explicit WHEN TO USE and WHEN NOT TO USE sections identify suitable deterministic calculations, numerical-input requirements, and unsuitable qualitative reasoning. The disambiguation section also routes chained jobs to omni_batch_calculate and schema inspection to omni_describe_solver.

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

Deploy Server

Other Tools