Skip to main content
Glama

borbur.net salary and tax calculators

US take-home pay 2026 (federal)

us_net_salary
Read-onlyIdempotent

US take-home pay in 2026 for a single filer with the standard deduction: federal income tax plus Social Security (6.2% up to $184,500) and Medicare (1.45%, +0.9% above $200,000). No state income tax. Source: https://borbur.net/tools/us-salary-in-spain/

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gross": "<gross>"
    },
    "name": "us_net_salary"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossYesGross annual salary in US dollars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, and the description adds genuinely new behavioral context: the exact tax components, the Social Security wage cap ($184,500), the 0.9% Medicare surtax threshold, and the filing assumptions. It still doesn't say whether the answer is a single net figure or a breakdown, but the assumption disclosure is strong.

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?

Purpose and unit of measure are front-loaded, followed by the rate table and the source link; nothing is redundant. The middle clause is dense with figures but each earns its place as verifiable methodology.

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 one-parameter, no-output-schema calculator this covers assumptions, tax components and provenance well. The main residual gap is that it never states what the returned value looks like (net total versus itemized breakdown), which matters slightly more given there is no output schema.

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 coverage is 100% and the sole parameter is documented as 'Gross annual salary in US dollars,' so the schema carries the load. The description's 'single filer with the standard deduction' framing implicitly tells the caller which gross figure the input represents (annual, pre-tax, US-based), but adds no format or boundary detail beyond that.

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 concrete computation (US take-home pay for 2026) and pins the scope precisely: single filer, standard deduction, federal only, no state income tax. That makes it clearly distinguishable from country-swap siblings like us_salary_in_spain, though no sibling is named explicitly.

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 implied rather than stated: the single-filer/standard-deduction assumptions signal who this applies to, and 'No state income tax' implicitly excludes state-level estimates. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for other filing statuses.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources