ScorpTech x402 Tools

Wage Calc

wage_calc

Read-onlyIdempotent

Gross pay in exact cents. Hourly: regular hours at the rate, overtime hours at a multiplier (default 1.5) and double-time hours at a multiplier (default 2). Weekly: hours above the threshold (default 40) are overtime. Salary: the annual amount is split across 52, 26, 24 or 12 periods so the paychecks add back to the annual amount. Extra straight-time hours are paid at annual / 2080 (52 × 40). Overtime and double-time hours use that same base rate times their multipliers. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/wage-calc

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": {
      "rate": "<rate>"
    },
    "name": "wage_calc"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No		hourly
`rate`	Yes	Hourly rate, or the annual salary in salary mode
`hours`	No	Hours worked (weekly mode, or extra hours on top of a salary)
`dtHours`	No
`otHours`	No
`periods`	No	Salary: paychecks per year
`dtMultiplier`	No	Default 2
`otMultiplier`	No	Default 1.5
`regularHours`	No
`weeklyThreshold`	No	Weekly mode: hours before overtime, default 40

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover safety and idempotency; the description usefully adds that output is exact cents, pricing is $0.001 USDC per successful call via x402 on Solana, and an HTTPS alternative exists. It omits payment/auth mechanics, failure charging, rate limits, and response shape.

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?

Front-loaded with the output unit, then mode-specific rules, pricing, and endpoint in a compact paragraph. It is efficient, though the run-on structure could be easier to scan than separate bullets.

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 10-parameter calculator with no output schema, it covers the calculation rules, defaults, and output unit well. It still leaves input units for rate and the exact response envelope/error behavior unspecified, which are meaningful gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 60% schema coverage, the description compensates substantially: it defines hourly/weekly/salary semantics, maps regular, overtime, and double-time hours, gives multiplier and threshold defaults, and explains the 2080 divisor for salary extra hours. It also clarifies salary periods and the dual meaning of rate, adding meaning well beyond the schema descriptions.

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?

States the core operation and output precisely: gross pay in exact cents, with three named modes. It does not explicitly distinguish itself from neighboring finance tools such as prorate or invoice_total, so it stops short of 5.

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

Usage Guidelines3/5

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

Explains how the three modes are calculated and gives defaults, which helps an agent infer when each mode applies. However, it never states when to choose wage_calc over another tool, nor any exclusions or prerequisites; usage is implied rather than explicit.

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

All ScorpTech x402 Tools 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?