Skip to main content
Glama

Estimate My Paycheck

Bonus after taxes

calculate_bonus_tax
Read-onlyIdempotent

What a bonus check pays after the flat 22% federal supplemental withholding, FICA and state tax, and how much of the federal withholding comes back (or is still owed) at tax time, on top of a salary, 2026 rules (IRS Pub. 15).

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": {
      "state": "<state>",
      "bonus": "<bonus>",
      "salary": "<salary>"
    },
    "name": "calculate_bonus_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
bonusYesBonus in dollars.
stateYesTwo-letter state code or name: TX, CA, new-york, DC.
salaryYesAnnual gross salary in dollars. Give this or hourly_rate.
tax_yearNoTax year, 2026 or 2027. Default: the year in force today (2026 now; 2027 from January 1, 2027).
filing_statusNoDefault single.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tax_year
      Added value: +{
      +  "description": "Tax year, 2026 or 2027. Default: the year in force today (2026 now; 2027 from January 1, 2027).",
      +  "example": 2026,
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.8/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, closed-world), so the description's job is to explain the computation, which it does well: it enumerates the withholding components applied and states that the result includes both net pay and the reconciliation of federal withholding at filing time. It does not discuss rounding, assumptions, or limits of the flat-22% shortcut, which would be the remaining valuable detail.

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?

It is a single front-loaded sentence with no filler; each clause adds a distinct element (withholding components, refund/owed outcome, salary context, rule set). The sentence is long and comma-chained, which slightly hurts scannability but wastes nothing.

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 a read-only calculator with five fully documented parameters and no output schema, the description carries the necessary burden by explaining both what goes into the number and what the returned figure represents (net bonus and federal withholding returned or still owed). Nothing an agent needs in order to select and call it 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?

Schema coverage is 100%, so every parameter is already documented, and the description only reinforces state tax and salary as inputs. Its mention of '2026 rules (IRS Pub. 15)' adds context for the tax_year parameter but slightly under-describes the schema's 2027 option, leaving the baseline of 3 appropriate.

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 precisely what is computed: post-withholding bonus pay (22% federal supplemental, FICA, state) plus the eventual refund/amount-owed on the federal piece. The verb is implicit ('what a bonus check pays') rather than an explicit 'calculates', and nothing names the siblings calculate_paycheck or compare_states for contrast, so it stops short of full 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 by the word 'bonus' and the phrase 'on top of a salary', which signals this is for extra supplemental income rather than a normal paycheck. There is no explicit statement of when to prefer this over calculate_paycheck, and no exclusions or prerequisites are given.

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