Geo-Parity

Compare contractor vs employee net take-home

compare_contract

Read-onlyIdempotent

Compute gross-to-net parity between a self-employed contractor hourly rate and an employee (W2/EOR) hourly rate, accounting for self-employment/income tax and self-paid health insurance, and return the break-even contractor rate. Uses transparent effective-rate tax presets per country, all overridable. Estimates only — not tax advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hours`	No	Hours per week (default 40).
`ctRate`	No	Override contractor effective tax rate, percent (e.g. 32).
`health`	No	Annual self-paid health insurance (USD); defaults to the country preset.
`country`	No	Country code for tax presets.	US
`empRate`	No	Override employee effective tax rate, percent (e.g. 24).
`taxMode`	No	'brackets' uses progressive 2025 schedules (US and GB only; falls back to flat elsewhere — response echoes the mode).
`expenses`	No	Annual business expenses (USD, default 0).
`employeeRate`	Yes	Employee/W2/EOR hourly rate (USD).
`employeeWeeks`	No	Employee paid weeks (default 52).
`contractorRate`	Yes	Self-employed hourly rate (USD).
`contractorWeeks`	No	Contractor paid/billable weeks (default 48).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`employee`	No
`contractor`	No
`breakevenRate`	No
`netDifference`	No
`contractorProfitable`	No

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark it read-only and idempotent; the description adds meaningful behavior beyond that: it relies on country-specific effective-rate tax presets, supports overrides, and is expressly an estimate, not tax advice. This helps set expectations about accuracy and configurability.

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?

The description is three sentences, front-loaded with the core computation, then method and caveat. No sentence is wasted; each earns its place.

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 an 11-parameter tool with a rich output schema, the description covers the central calculation, overridability, country-preset behavior, and estimation caveat. Remaining details like country-specific fallbacks are present in the schema, so nothing needed for correct invocation is missing.

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?

The input schema already documents all 11 parameters with descriptions, and schema coverage is 100%, so the baseline applies. The description reinforces the role of tax presets and overrides but does not add substantial meaning beyond what each parameter description already provides.

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 names the exact computation (gross-to-net parity between contractor and employee hourly rates), the inputs considered (self-employment/income tax, self-paid health insurance), and the output (break-even contractor rate). This clearly distinguishes it from sibling cost/salary tools.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool: comparing net take-home between a self-employed contractor rate and an employee/W2/EOR rate. It does not explicitly name alternatives or exclusions, but the use case is specific enough to route an agent.

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

All Geo-Parity 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.9/5.0

Disambiguation3/5

Several tools occupy adjacent territory: check_travel_residency explicitly supersedes check_residency, check_schengen, and check_tax_residency_risk, and the cost-of-living family (arrival_cost, compare_total_cost, compare_housing, estimate_micro_costs, calculate_ppp, localize_salary) has overlapping price-level concepts. The detailed descriptions mostly clarify boundaries, but an agent selecting by name alone could easily pick the wrong residency or cost tool.

Naming Consistency4/5

Most tools follow a clean verb_noun snake_case pattern with recognizable prefixes (compare_*, check_*, find_*, calculate_*), which makes the set predictable. Deviations like arrival_cost, passport_power, required_rate, and the acronym-heavy calculate_ppp keep it from being perfectly uniform.

Tool Count3/5

26 tools is a heavy surface, and at least three of the check_* tools are explicitly superseded by check_travel_residency, adding redundant weight. The broad geo-arbitrage/nomad domain justifies much of the breadth, but the set feels closer to a full toolkit than a focused server.

Completeness4/5

The toolset covers the core remote-work and geo-arbitrage decision space: cost of living, purchasing power, tax residency risk, nomad visas, housing, healthcare, climate, connectivity, holidays, salary localization, FIRE, livability, and even team timezone planning. Gaps are minor—no family-size cost tool, no immigration/citizenship pathway data, and no dedicated safety/crime dataset beyond the livability composite—but agents can work around them.

Resources

Need Help?