Skip to main content
Glama

Arc & Ledger Tax Reference

by com.arcandledger

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
NameRequiredDescriptionDefault
briefNoSet true for a shorter answer: options come back as path + fit only, without the descriptions.
ability_to_payYesYour 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).
balance_owed_usdYesTotal amount owed to the IRS including tax, penalties, and interest (a rough figure is fine).
tax_account_typeNoCoarse, 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_filedNoWhether 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_penaltiesNoWhether the balance includes failure-to-file or failure-to-pay penalties, so penalty abatement may reduce it. Defaults to true.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
relayYesInstruction to the calling assistant: relay figures and dates verbatim (identical on every response).
next_stepYesA single review link appropriate to this server surface.
disclaimerYesGeneral-information disclaimer (identical on every response).
source_urlYesOfficial IRS or FinCEN authority to review before relying on the result.
server_versionNoServer release that produced this response (matches GET /version).

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, ensuring safe, read-only behavior. The description adds value by emphasizing the tool is educational and not a guarantee of IRS approval, which is critical for managing user expectations.

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?

The description is two sentences, front-loading the purpose and providing a critical caveat. Every word earns its place; no unnecessary information.

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 6 parameters (2 required), an output schema, and clear annotations, the description adequately covers the tool's purpose and limitations. The output schema would handle return value details, so the description focuses on usage intent.

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?

The input schema has 100% coverage with detailed parameter descriptions, so the baseline is 3. The tool description does not add additional parameter semantics beyond what the schema already provides, but the schema itself is thorough.

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?

The description clearly states it screens IRS payment/collection alternatives based on specific inputs (balance, compliance, ability to pay, tax account type). It distinguishes itself from sibling tools (e.g., check_5472_obligation, check_fbar_fatca) which focus on specific tax obligations or forms, whereas this is a general resolution screening tool.

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?

The description explicitly says 'Use to screen...' indicating when to use the tool. It also qualifies the output as 'educational fit screen, not a promise'. While it doesn't explicitly state when not to use it or name alternatives, the context from sibling tools implies its role as a broad screening tool.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool addresses a distinct tax topic or action, such as screening obligations, checking eligibility, estimating amounts, or explaining documents. There is no overlap in purpose, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun or verb_phrase pattern (e.g., check_*, estimate_*, explain_*, decode_*, deadline_calendar). The naming is predictable and clear across the set.

Tool Count5/5

With 13 tools, the server covers a broad range of tax reference needs without being overwhelming. Each tool has a clear purpose and the count is well-suited for the domain.

Completeness4/5

The tools cover common tax reference tasks like screening obligations, estimating penalties, explaining forms, and checking deadlines. A minor gap is the lack of a general tax liability estimator, but overall the set is comprehensive for its stated purpose.

Resources