TrueCalci

Billable rate floor

billable_floor

Read-onlyIdempotent

Solve the exact minimum billable hourly rate required to achieve a target net spendable cash income, factoring in unpaid weeks, non-billable administrative drag, deductible overhead, health insurance, and SECA self-employment taxes.

Behavior: Deterministic, idempotent calculation with zero external side effects. Numerically solves the gross revenue needed so that Gross - Expenses - Health - SECA Tax - Income Tax equals Target Net Cash. Divides required gross revenue by actual billable hours (accounting for vacation weeks and non-billable admin/marketing percentage) to derive the hourly billable floor.

Usage Guidelines: Use when a freelancer, consultant, or agency owner wants to set their baseline hourly rate to support their personal lifestyle budget. Do not use when directly benchmarking against a specific W-2 salary offer; use contractor_parity instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`as_of_date`	Yes	Civil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.
`filingStatus`	No	IRS income tax filing status: 'single' for unmarried individual or 'mfj' for married filing jointly.	single
`targetNetCash`	Yes	Desired annual net spendable cash take-home after all taxes and business expenses in USD ($/yr). Must be positive.
`vacationWeeks`	No	Number of unpaid vacation, holiday, and sick weeks off planned per year (e.g. 4 for 4 weeks).
`annualExpenses`	No	Annual tax-deductible business operating expenses in USD ($/yr) (software, office, hardware, insurance).
`nonBillablePercent`	No	Percentage of total working hours lost to non-billable business activities like admin, sales, and invoicing (e.g. 28 for 28%).
`healthInsuranceAnnual`	No	Annual out-of-pocket health insurance premium in USD ($/yr) paid directly by the freelancer.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`currency`	No
`metadata`	No
`economics`	No
`disclaimer`	No
`naive_rate`	No
`minor_units`	No
`naive_economics`	No
`naive_shortfall`	No
`target_net_cash`	No
`time_allocation`	No
`statutory_authority`	No
`required_hourly_rate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

removedOutput schema / properties / optimal_hourly_rate

Removed value: -{
-  "type": [
-    "string",
-    "number",
-    "null"
-  ]
-}

addedOutput schema / properties / required_hourly_rate

Added value: +{
+  "type": [
+    "string",
+    "number",
+    "null"
+  ]
+}

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "currency": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "disclaimer": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "economics": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "metadata": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "minor_units": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "naive_economics": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "naive_rate": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "naive_shortfall": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "optimal_hourly_rate": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "statutory_authority": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "target_net_cash": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "time_allocation": {
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 26, 2026

addedInput schema / properties / as_of_date

Added value: +{
+  "description": "Civil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.",
+  "example": "2026-09-26",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "targetNetCash"
-]New value: +[
+  "targetNetCash",
+  "as_of_date"
+]

Changed1 schema field changedSep 24, 2026
- removedInput schema / properties / targetNetCash / default
```
Removed value: -120000
```

Changed6 schema fields changedSep 5, 2026

changedInput schema / properties / annualExpenses / description

Previous value: -"Annual business operating expenses ($/yr)"New value: +"Annual tax-deductible business operating expenses in USD ($/yr) (software, office, hardware, insurance)."

addedInput schema / properties / filingStatus / description

Added value: +"IRS income tax filing status: 'single' for unmarried individual or 'mfj' for married filing jointly."

changedInput schema / properties / healthInsuranceAnnual / description

Previous value: -"Annual out-of-pocket health insurance premium ($/yr)"New value: +"Annual out-of-pocket health insurance premium in USD ($/yr) paid directly by the freelancer."

changedInput schema / properties / nonBillablePercent / description

Previous value: -"Percentage of working hours lost to admin, sales, and invoicing %"New value: +"Percentage of total working hours lost to non-billable business activities like admin, sales, and invoicing (e.g. 28 for 28%)."

changedInput schema / properties / targetNetCash / description

Previous value: -"Target annual net spendable cash take-home ($/yr)"New value: +"Desired annual net spendable cash take-home after all taxes and business expenses in USD ($/yr). Must be positive."

changedInput schema / properties / vacationWeeks / description

Previous value: -"Planned vacation weeks off per year"New value: +"Number of unpaid vacation, holiday, and sick weeks off planned per year (e.g. 4 for 4 weeks)."

First observedSep 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so 'deterministic, idempotent, zero side effects' is partly redundant. What is not redundant is the disclosed solution chain (Gross - Expenses - Health - SECA - Income Tax = Target Net Cash) and the derivation of the hourly floor from actual billable hours, which tells the agent how the number is produced rather than just that it is safe.

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 core computation before the behavioral block and the usage routing; the labeled Behavior/Usage structure makes it scannable. It runs a bit long and restates safety traits the annotations already carry, but no sentence is filler in a way that harms selection.

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?

With an output schema present, rich annotations, and 100% schema coverage, the description only needs to add algorithmic intent and routing, and it does both. The agent knows what the tool computes, when to pick it, and which sibling to prefer otherwise.

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 every parameter is already documented in the schema; the baseline is 3. The description loosely maps its listed factors onto parameters (unpaid weeks -> vacationWeeks, admin drag -> nonBillablePercent, health -> healthInsuranceAnnual), but adds no units, formats or defaults beyond what the schema already states.

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 precise verb+resource: solve the minimum billable hourly rate to hit a target net cash income, and enumerates the factors it accounts for (unpaid weeks, admin drag, overhead, health insurance, SECA). It explicitly distinguishes itself from contractor_parity, so an agent can route correctly without opening either schema.

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?

Gives an explicit use case (freelancer/consultant/agency owner setting a baseline lifestyle-supporting rate) and an explicit exclusion with the named alternative: do not use for benchmarking against a W-2 salary offer, use contractor_parity instead.

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

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