Skip to main content
Glama

TrueCalci

by com.truecalci
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
as_of_dateYesCivil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.
filingStatusNoIRS income tax filing status: 'single' for unmarried individual or 'mfj' for married filing jointly.single
targetNetCashYesDesired annual net spendable cash take-home after all taxes and business expenses in USD ($/yr). Must be positive.
vacationWeeksNoNumber of unpaid vacation, holiday, and sick weeks off planned per year (e.g. 4 for 4 weeks).
annualExpensesNoAnnual tax-deductible business operating expenses in USD ($/yr) (software, office, hardware, insurance).
nonBillablePercentNoPercentage of total working hours lost to non-billable business activities like admin, sales, and invoicing (e.g. 28 for 28%).
healthInsuranceAnnualNoAnnual out-of-pocket health insurance premium in USD ($/yr) paid directly by the freelancer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+]
  2. Changed1 schema field changed
    • removedInput schema / properties / targetNetCash / default
      Removed value: -120000
  3. Changed6 schema fields changed
    • 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)."
  4. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior; the description echoes that but adds real value by stating the exact equation Gross - Expenses - Health - SECA Tax - Income Tax = Target Net Cash and explaining how billable hours are derived from vacation weeks and non-billable percentage. No contradiction with annotations.

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?

Organized into three efficient sections: overview, behavior, and usage. Every sentence contributes either to understanding the calculation, clarifying side effects, or distinguishing the tool from contractor_parity. No filler or redundant restatement of schema details.

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?

For a deterministic calculation tool with fully documented parameters and annotations, the description is complete: it gives the computational model, output definition, required date rule-pack behavior, usage context, and sibling exclusion. Even without an output schema, the return value ('hourly billable floor') is unambiguous.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond individual field descriptions by showing how targetNetCash, annualExpenses, healthInsuranceAnnual, vacationWeeks, and nonBillablePercent interact in a single calculation, clarifying the relationship between parameters and the derived hourly floor.

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 opens with a specific verb and resource: 'Solve the exact minimum billable hourly rate required to achieve a target net spendable cash income' and enumerates the contributing factors. It also names the sibling alternative (contractor_parity), so an agent can distinguish this tool without opening its 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?

Provides explicit 'Use when' context for freelancers/consultants/agency owners setting a baseline rate and explicit 'Do not use when' guidance directing the agent to contractor_parity for W-2 salary comparisons. This is clear routing between siblings.

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

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