Skip to main content
Glama

converters_self_employment_tax

Read-onlyIdempotent

Self-employment tax: 2026 wage base, Medicare and Additional Medicare

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": {
      "netProfit": "<netProfit>"
    },
    "name": "converters_self_employment_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoYYYY-MM-DD. Payments due on or before this date are treated as past when spreading what is still to pay. Default: all four are still ahead.
stateNoWith includeIncomeTax: a US state (two-letter code or name) to add that state's income tax on the profit.
methodNo'even' (default): four equal payments. 'annualized': each payment follows the income earned so far (needs cumulativeProfit); good for seasonal income.
w2WagesNoW-2 wages from a job in the same year. They use up part of the Social Security wage base and count toward the Additional Medicare threshold.
netProfitYesNet self-employment profit for the year, in US dollars.
filingStatusNoFederal filing status. Default single.
paymentsMadeNoEstimated payments already made this year. Counts against the yearly total in the 'remaining' block and the safe harbour.
priorYearAgiNoWith priorYearTax: last year's adjusted gross income; above $150,000 ($75,000 married filing separately) the safe harbour is 110% of last year's tax.
priorYearTaxNoWith includeIncomeTax: last year's federal total tax (self-employment plus income tax), for the IRS safe-harbour test on the federal part (100% of last year's tax, or 110% if priorYearAgi is above the threshold).
ytdWithholdingNoWith includeIncomeTax: federal income tax already withheld this year (for example from a W-2 job). Counts against the yearly total in the 'remaining' block and the safe harbour.
cumulativeProfitNoWith method 'annualized': net profit earned so far through Mar 31, May 31 and Aug 31 (cumulative, rising, not above netProfit). netProfit is the full-year figure.
includeIncomeTaxNotrue adds federal income tax (2026 brackets, standard deduction, after the half self-employment tax deduction) so quarterlyPayment is the whole estimated payment. Default false: quarterlyPayment is the self-employment tax divided by 4.
priorYearStateTaxNoWith includeIncomeTax and state: last year's state income tax, for the state's own safe-harbour test. Without it the state test is 90% of this year's state tax. priorYearTax is last year's federal total (self-employment plus income tax) and is tested against the federal figure only.

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. Changed7 schema fields changed
    • addedInput schema / properties / asOf
      Added value: +{
      +  "description": "YYYY-MM-DD. Payments due on or before this date are treated as past when spreading what is still to pay. Default: all four are still ahead.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / cumulativeProfit
      Added value: +{
      +  "description": "With method 'annualized': net profit earned so far through Mar 31, May 31 and Aug 31 (cumulative, rising, not above netProfit). netProfit is the full-year figure.",
      +  "items": {
      +    "minimum": 0,
      +    "type": "number"
      +  },
      +  "maxItems": 3,
      +  "minItems": 3,
      +  "type": "array"
      +}
    • addedInput schema / properties / method
      Added value: +{
      +  "description": "'even' (default): four equal payments. 'annualized': each payment follows the income earned so far (needs cumulativeProfit); good for seasonal income.",
      +  "enum": [
      +    "even",
      +    "annualized"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / paymentsMade
      Added value: +{
      +  "description": "Estimated payments already made this year. Counts against the yearly total in the 'remaining' block and the safe harbour.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / priorYearStateTax
      Added value: +{
      +  "description": "With includeIncomeTax and state: last year's state income tax, for the state's own safe-harbour test. Without it the state test is 90% of this year's state tax. priorYearTax is last year's federal total (self-employment plus income tax) and is tested against the federal figure only.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • changedInput schema / properties / priorYearTax / description
      Previous value: -"With includeIncomeTax: last year's total tax, for the IRS safe-harbour alternative (100% of last year's tax, or 110% if priorYearAgi is above the threshold)."New value: +"With includeIncomeTax: last year's federal total tax (self-employment plus income tax), for the IRS safe-harbour test on the federal part (100% of last year's tax, or 110% if priorYearAgi is above the threshold)."
    • addedInput schema / properties / ytdWithholding
      Added value: +{
      +  "description": "With includeIncomeTax: federal income tax already withheld this year (for example from a W-2 job). Counts against the yearly total in the 'remaining' block and the safe harbour.",
      +  "minimum": 0,
      +  "type": "number"
      +}
  3. Changed4 schema fields changed
    • addedInput schema / properties / includeIncomeTax
      Added value: +{
      +  "description": "true adds federal income tax (2026 brackets, standard deduction, after the half self-employment tax deduction) so quarterlyPayment is the whole estimated payment. Default false: quarterlyPayment is the self-employment tax divided by 4.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / priorYearAgi
      Added value: +{
      +  "description": "With priorYearTax: last year's adjusted gross income; above $150,000 ($75,000 married filing separately) the safe harbour is 110% of last year's tax.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / priorYearTax
      Added value: +{
      +  "description": "With includeIncomeTax: last year's total tax, for the IRS safe-harbour alternative (100% of last year's tax, or 110% if priorYearAgi is above the threshold).",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "With includeIncomeTax: a US state (two-letter code or name) to add that state's income tax on the profit.",
      +  "type": "string"
      +}
  4. Changed3 schema fields changed
    • 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 / netProfit / description
      Added value: +"Net self-employment profit for the year, in US dollars."
    • addedInput schema / properties / w2Wages
      Added value: +{
      +  "description": "W-2 wages from a job in the same year. They use up part of the Social Security wage base and count toward the Additional Medicare threshold.",
      +  "minimum": 0,
      +  "type": "number"
      +}
  5. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. Beyond that the description adds nothing about behavior — that this returns quarterly payment amounts, that method 'annualized' changes the computation, or that the safe-harbour and income-tax blocks only appear under certain flags — all of which live only in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no filler, but it is under-specified rather than concise: a ten-word fragment for a 13-parameter financial calculator omits the output framing entirely. There is nothing to trim, but also nothing front-loaded beyond a topic tag.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, 13 parameters, and conditional behavior (includeIncomeTax, state tax, annualized method, safe harbour), yet the description never states what a call returns or how the modes differ. The schema compensates for parameters, but the overall definition leaves the agent without the picture needed to select this tool confidently.

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%, so the schema already documents all 13 parameters in detail, including defaults and conditional dependencies. The description supplies no additional parameter meaning, which is acceptable at this coverage level but earns no credit above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text reads as a topic label ('Self-employment tax: 2026 wage base, Medicare and Additional Medicare') rather than a verb+resource statement; no verb such as 'calculate' or 'estimate' tells the agent what the tool produces. It does narrow the domain to self-employment tax components, but an agent could not distinguish it from converters_us_income_tax or converters_paycheck on the description alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives such as the US income tax or paycheck converters, and no prerequisites noted. The agent must infer the use case entirely from the tool name.

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