Skip to main content
Glama

tax_us.federal_income

Read-onlyIdempotent

Determine US Federal Income Tax liability based on income and filing status. Accurately compute your tax burden using current IRS progressive brackets for various filing categories.

Instructions

미국 연방 소득세(일반 세율)를 계산한다. IRS 2025·2026 tax year, 7개 누진 구간, 4개 신고 유형이며 qualifying_surviving_spouse 는 공동 신고 표를 쓴다. 금액은 USD Decimal 문자열이고 기본은 소수 둘째 자리 HALF_UP이다. apply_standard_deduction=true 이면 taxable_income 을 AGI 로 보고 표준공제를 뺀다. 이미 공제를 뺀 과세표준에 true 를 주면 공제가 두 번 빠지고, 장기 양도소득이나 FICA 는 반영하지 않는다.

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": {
      "taxable_income": "<taxable_income>",
      "filing_status": "<filing_status>",
      "year": "<year>"
    },
    "name": "tax_us.federal_income"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
as_ofNo
decimalsNo
roundingNoHALF_UP
filing_statusYes
taxable_incomeYes
include_proposedNo
apply_standard_deductionNo

Output Schema

NameRequiredDescriptionDefault
taxYes
_metaNo서버가 붙이는 영수증(integrity), 엔진, 힌트
traceYes계산 근거(tool, formula, inputs, steps, output)
breakdownYes
filing_statusYes
marginal_rateYes
policy_sha256Yes
policy_sourceYes
policy_statusYes
effective_rateYes
policy_versionYes적용된 정책 문서의 식별 정보
policy_audit_idYes
policy_citationsYes정책의 근거 조문
standard_deductionYes
policy_effective_toYes
policy_effective_dateYes
taxable_income_after_deductionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description adds real substance beyond them: the bracket structure, the QSS-uses-joint-table rule, the USD Decimal input convention, the default HALF_UP/two-decimal rounding, and a concrete double-deduction failure mode. The scope exclusions further prevent silent misuse.

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?

Front-loaded with purpose and scope, then parameter-relevant rules and caveats; each sentence contributes a distinct constraint. It is dense for a single paragraph but not padded, with only minor redundancy between the deduction rule and the double-deduction warning.

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 formatting need not be described, and the description covers the tax logic, unit/rounding conventions, and misuse traps well. The only shortfall is the two undocumented optional parameters, which slightly under-equips the agent for a full-fidelity call.

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 0% across 8 parameters, so the description carries the load, and it explains year, decimals, rounding, filing_status (including QSS mapping), taxable_income format, and apply_standard_deduction in detail. Two parameters, as_of and include_proposed, are never mentioned, leaving a real gap.

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

Purpose5/5

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

States a specific verb and resource ('미국 연방 소득세(일반 세율)를 계산한다') and bounds it by year (2025·2026), bracket count, and filing types. The final clause explicitly excludes long-term capital gains and FICA, which maps onto siblings tax_us.capital_gains and tax_us.fica, so an agent can separate it from the other US tax tools without opening a schema.

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

Usage Guidelines4/5

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

It gives clear context (ordinary-rate federal income tax, ordinary income only) and says what is out of scope (capital gains, FICA), plus a specific warning about when apply_standard_deduction should and should not be true. It stops short of naming the alternative tools by exact name, so routing depends on inference from the domain exclusions.

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

Deploy Server

Other Tools