Geo-Parity

Compute the required freelance hourly rate

required_rate

Read-onlyIdempotent

Given a desired annual net income, compute the freelance hourly and day rate required after taxes, self-paid health insurance, weeks off, and billable utilization. Uses the same per-country effective-rate presets as compare_contract; all overridable. Estimates only — not tax advice.

Input Schema

Name	Required	Description	Default
`hours`	No	Hours per week (default 40).
`health`	No	Annual self-paid health insurance (USD); defaults to the country preset.
`country`	No		US
`taxRate`	No	Override effective tax rate, percent (e.g. 32).
`expenses`	No	Annual business expenses (USD, default 0).
`weeksOff`	No	Unpaid weeks off per year (default 4).
`desiredNet`	Yes	Desired annual net take-home (USD).
`utilization`	No	Billable share of working hours, 0–1 (default 0.75).

Output Schema

Name	Required	Description	Default
`ok`	No
`dayRate`	No
`hourlyRate`	No
`billableHours`	No
`requiredGross`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / examples

Added value: +[
+  {
+    "country": "US",
+    "desiredNet": 100000,
+    "utilization": 0.7,
+    "weeksOff": 6
+  }
+]

First observedSep 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds genuine context beyond them: the estimate is after taxes, health insurance, weeks off, and utilization, that presets are shared with compare_contract, that all inputs are overridable, and the 'not tax advice' caveat.

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?

Three tight sentences, front-loaded with the core purpose, then the preset relationship, then the disclaimer. No filler; each sentence earns its place.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. The description covers purpose, preset sourcing, and the estimate disclaimer, leaving it essentially complete for an 8-param calculation tool.

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 high (88%), setting a baseline of 3, but the description adds meaning by mapping the computation to the parameter categories (taxes, health, weeks off, utilization) and explicitly stating that the country presets are 'all overridable', which tells the agent every default can be replaced.

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?

The description states a specific verb+resource ('compute the freelance hourly and day rate') and clarifies the driving input ('given a desired annual net income'). It cross-references the sibling compare_contract by noting it shares the same per-country presets, giving reasonable differentiation.

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?

Usage is only implied: the tool is for freelancers who want to back into a rate from a target net income. There is no explicit when-to-use vs when-not, no mention of alternatives, and no prerequisites beyond the input scenario.

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

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?