Skip to main content
Glama

converters_us_income_tax

Read-onlyIdempotent

US federal income tax estimate with 2026 brackets, filing status, deductions, FICA and state tax

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "converters_us_income_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoWith grossIncome: US state (two-letter code or name) to add that state's 2026 income tax.
deductionNoWith grossIncome. Default standard (2026 amount for the filing status).
grossIncomeNoGross income before deductions (wages or profit). The standard or itemized deduction is applied for you, and FICA and optional state tax are added. Send this OR taxableIncome.
filingStatusNoFederal filing status. Default single.
selfEmployedNoWith grossIncome: treat the income as self-employment profit (self-employment tax instead of employee FICA).
taxableIncomeNoIncome after deductions. Send this OR grossIncome.
preTaxDeductionsNoWith grossIncome: yearly pre-tax deductions such as traditional 401(k). Lowers income tax but not FICA.
itemizedDeductionsNoWith deduction 'itemized': the total of your itemized deductions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed9 schema fields changed
    • addedInput schema / properties / deduction
      Added value: +{
      +  "description": "With grossIncome. Default standard (2026 amount for the filing status).",
      +  "enum": [
      +    "standard",
      +    "itemized"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / filingStatus
      Added value: +{
      +  "description": "Federal filing status. Default single.",
      +  "enum": [
      +    "single",
      +    "married-joint",
      +    "married-separate",
      +    "head-of-household"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / grossIncome
      Added value: +{
      +  "description": "Gross income before deductions (wages or profit). The standard or itemized deduction is applied for you, and FICA and optional state tax are added. Send this OR taxableIncome.",
      +  "type": "number"
      +}
    • addedInput schema / properties / itemizedDeductions
      Added value: +{
      +  "description": "With deduction 'itemized': the total of your itemized deductions.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / preTaxDeductions
      Added value: +{
      +  "description": "With grossIncome: yearly pre-tax deductions such as traditional 401(k). Lowers income tax but not FICA.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / selfEmployed
      Added value: +{
      +  "description": "With grossIncome: treat the income as self-employment profit (self-employment tax instead of employee FICA).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "With grossIncome: US state (two-letter code or name) to add that state's 2026 income tax.",
      +  "type": "string"
      +}
    • addedInput schema / properties / taxableIncome / description
      Added value: +"Income after deductions. Send this OR grossIncome."
    • removedInput schema / required
      Removed value: -[
      -  "taxableIncome"
      -]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and openWorldHint false, so the safety profile is fully covered. The description adds genuine behavioral context beyond that: the standard or itemized deduction is applied automatically, FICA is added, state tax is optional, and self-employment tax replaces employee FICA when selfEmployed is set. It omits whether the output is a single figure or a breakdown and does not caveat that results are estimates.

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?

A single front-loaded phrase listing the computed components, with no filler or repetition. It is efficient, though the absence of a verb or any sentence structure makes it read as a label rather than an explanation.

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 an 8-parameter, all-optional pure-calculation tool with no output schema, the definition covers the key modes: gross income vs taxable income, deduction handling, FICA, self-employment, and optional state. What remains thin is the expected result shape and the estimate-not-advice caveat, both minor for a deterministic calculator whose annotations already signal a safe read.

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 description coverage is 100% and the per-parameter text is already detailed with conditionals and defaults, so the schema carries the semantic load. The description's only additions are the 2026 tax year and the fact that deduction/FICA/state handling is automatic, which is useful but marginal against the schema.

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 names a specific computation and its components (2026 federal brackets, filing status, deductions, FICA, optional state tax), so an agent knows it is an estimate tool rather than a lookup. It does not explicitly distinguish itself from near siblings such as converters_state_tax or converters_self_employment_tax, leaving overlap for the agent to resolve.

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 gives no when-to-use or when-not-to-use guidance and does not route to sibling tools. Usage conditions live only in the parameter descriptions ('Send this OR taxableIncome', 'With grossIncome'), which implicitly define two input modes but never state which sibling calculator to prefer.

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