decisions

Freelance Rate Floor

freelance_rate_floor

Read-onlyIdempotent

Freelance Rate Floor — Calculates the hourly rate a freelancer must bill to match a given salary after self-employment tax and lost benefits. Returns a one-line verdict plus a link to the full interactive page with the numbers pre-filled. Accepts only numbers and enums.

Input Schema

TableJSON Schema

Name	Required	Description
`year`	No	Tax year, e.g. 2026. Omit to use the current tax year.
`stateCode`	Yes	Two-letter US state code, e.g. CA, TX, NY.
`filingStatus`	Yes	One of: single, married_joint, married_separate, head_of_household.
`currentSalary`	Yes	A non-negative number (US dollars unless the field name says otherwise).
`annualBenefitsValue`	Yes	A non-negative number (US dollars unless the field name says otherwise).
`billableHoursPerYear`	No	A non-negative number (US dollars unless the field name says otherwise).

TDQS

A4/5.0

Behavior4/5

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

Annotations indicate readOnly and idempotent, and the description adds behavioral context: returns a one-line verdict plus a link with pre-filled numbers. No side effects or destructive actions are mentioned, which is consistent.

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?

Two sentences, no excess. The first sentence covers purpose and output, the second adds input constraints and output format. Efficient and well-structured.

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 calculator tool with no output schema, the description adequately explains input constraints and output format (verdict + link). Could be more detailed about edge cases or the link behavior, but sufficient for most uses.

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?

All parameters have descriptions in the schema (100% coverage). The description adds only a general note about accepting numbers and enums, which does not significantly enhance understanding 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 states precisely what the tool computes (hourly rate to match salary after tax and benefits) and what it returns (verdict + link). It clearly distinguishes from sibling tools like best_filing_status or job_offer_worth_it.

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?

The description implies use for freelancers comparing salary to freelance rate, but does not explicitly say when to use this tool over siblings or when not to use it. No alternative tool names are provided.

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

All decisions tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation5/5

Each tool targets a distinct financial decision (filing status, freelancer rate, job offer, raise/bonus, Roth vs Traditional), with no overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent pattern of descriptive snake_case phrases, clearly indicating the decision type.

Tool Count4/5

Five tools is a reasonable number for a decision-support server, covering common personal finance scenarios without being excessive or too thin.

Completeness3/5

While core decisions are covered, there are notable gaps such as mortgage vs. rent, debt payoff strategies, or investment comparisons, which limit completeness for the full domain.

Resources

Need Help?