Arc & Ledger Tax Reference

Check IRS resolution options

check_resolution_options

Read-only

Use to screen general IRS payment and collection alternatives from a rough balance, filing-compliance status, ability-to-pay category, and coarse tax-account type when known. This is an educational fit screen, not a promise that the IRS will approve an option.

Input Schema

TableJSON Schema

Name	Required	Description
`brief`	No	Set true for a shorter answer: options come back as path + fit only, without the descriptions.
`ability_to_pay`	Yes	Your realistic ability to pay. can_pay_in_full_soon = you can clear the balance within 180 days; can_make_monthly_payments = a monthly amount but not in full; can_pay_little = only a very small monthly amount; cannot_pay_basic_living = paying the IRS would leave you unable to cover basic living expenses (financial hardship).
`balance_owed_usd`	Yes	Total amount owed to the IRS including tax, penalties, and interest (a rough figure is fine).
`tax_account_type`	No	Coarse, nonidentifying IRS account type. individual_income_tax includes Form 1040 income-tax balances, including a sole proprietor whose balance is on Form 1040. business_non_trust_fund_or_out_of_business covers non-trust-fund business tax or an out-of-business sole proprietor account. business_trust_fund covers in-business payroll or other trust-fund tax. Use unknown when unsure. Defaults to unknown.
`all_required_returns_filed`	No	Whether every required tax return has actually been FILED (even if the tax was not paid). Filing compliance is generally required before the IRS formalizes a collection alternative, but the exact account requirements control. Defaults to false.
`balance_includes_penalties`	No	Whether the balance includes failure-to-file or failure-to-pay penalties, so penalty abatement may reduce it. Defaults to true.

Output Schema

TableJSON Schema

Name	Required	Description
`relay`	Yes	Instruction to the calling assistant: relay figures and dates verbatim (identical on every response).
`next_step`	Yes	A single review link appropriate to this server surface.
`disclaimer`	Yes	General-information disclaimer (identical on every response).
`source_url`	Yes	Official IRS or FinCEN authority to review before relying on the result.
`server_version`	No	Server release that produced this response (matches GET /version).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / ability_to_pay / description

Previous value: -"Your realistic ability to pay. can_pay_in_full_soon = you can clear the balance within about 120-180 days; can_make_monthly_payments = a monthly amount but not in full; can_pay_little = only a very small monthly amount; cannot_pay_basic_living = paying the IRS would leave you unable to cover basic living expenses (financial hardship)."New value: +"Your realistic ability to pay. can_pay_in_full_soon = you can clear the balance within 180 days; can_make_monthly_payments = a monthly amount but not in full; can_pay_little = only a very small monthly amount; cannot_pay_basic_living = paying the IRS would leave you unable to cover basic living expenses (financial hardship)."

First observedJul 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond them: the result is an educational fit screen, not an IRS determination, which sets the expectation an agent needs when relaying output.

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

Conciseness5/5

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

Two sentences, zero waste: the first front-loads what the tool screens and from which inputs, the second immediately bounds the output. Every clause earns its place.

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?

With an output schema present, return values need not be explained here. The description adequately covers scope, input expectations and the educational caveat; only the meaning of a 'fit' result or any ranking of options is left unaddressed, which is a minor gap.

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 enums, defaults and meanings for all six parameters. The description only restates which inputs matter and adds 'when known' for optionality; it adds no format or interpretation detail beyond the schema. Baseline 3 is 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?

States a specific verb ('screen') and resource ('general IRS payment and collection alternatives'), and enumerates the inputs that drive it, so an agent knows exactly what the tool computes. It does not name or contrast any sibling (e.g. estimate_irs_penalty, check_5472_obligation), so differentiation relies on domain inference.

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?

Gives a clear use context: screen broadly from a rough balance, filing-compliance status, ability-to-pay category and coarse account type 'when known'. It also bounds the use case with 'educational fit screen, not a promise that the IRS will approve an option'. No explicit when-not or named alternative, but the context is easy to apply.

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

All Arc & Ledger Tax Reference tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.