Arc & Ledger Tax Tools

Check IRS resolution options

check_resolution_options

Read-only

Use this when someone owes the IRS back taxes and asks how to settle, get on a payment plan, lower what they owe, or stop collection. Screens which IRS paths may fit - short-term payment plan, current Simple Payment Plan or an installment agreement with financial review, Offer in Compromise (a fit-check only, never a promise of acceptance), Currently Not Collectible hardship status, and penalty abatement - and lists the forms needed (9465, 433-F/A/B, 656, 843, 8821, 2848) plus collection-statute context. A coarse tax_account_type improves the screen without identifying the taxpayer. Never guarantees an IRS outcome. Set brief:true for a shorter answer.

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	The arcandledger.com page that backs this answer.
`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)."

Changed2 schema fields changedJul 26, 2026

changedInput schema / properties / all_required_returns_filed / description

Previous value: -"Whether every required tax return has actually been FILED (even if the tax was not paid). The IRS will not approve any installment agreement, Offer in Compromise, or hardship status until you are filing-compliant. Defaults to false."New value: +"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."

addedInput schema / properties / tax_account_type

Added value: +{
+  "description": "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.",
+  "enum": [
+    "individual_income_tax",
+    "business_non_trust_fund_or_out_of_business",
+    "business_trust_fund",
+    "unknown"
+  ],
+  "type": "string"
+}

Changed1 schema field changedJul 26, 2026

changedOutput schema / properties / next_step / description

Previous value: -"A single human handoff to the firm."New value: +"A single review link appropriate to this server surface."

Changed2 schema fields changedJul 13, 2026

addedOutput schema / properties / relay

Added value: +{
+  "description": "Instruction to the calling assistant: relay figures and dates verbatim (identical on every response).",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "disclaimer",
-  "source_url",
-  "next_step"
-]New value: +[
+  "disclaimer",
+  "relay",
+  "source_url",
+  "next_step"
+]

Changed2 schema fields changedJul 12, 2026

addedInput schema / properties / brief

Added value: +{
+  "description": "Set true for a shorter answer: options come back as path + fit only, without the descriptions.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "disclaimer": {
+      "description": "General-information disclaimer (identical on every response).",
+      "type": "string"
+    },
+    "next_step": {
+      "description": "A single human handoff to the firm.",
+      "properties": {
+        "label": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "label",
+        "url"
+      ],
+      "type": "object"
+    },
+    "server_version": {
+      "description": "Server release that produced this response (matches GET /version).",
+      "type": "string"
+    },
+    "source_url": {
+      "description": "The arcandledger.com page that backs this answer.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "disclaimer",
+    "source_url",
+    "next_step"
+  ],
+  "type": "object"
+}

First observedJul 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish a safe read-only, closed-world profile, and the description adds genuine context beyond them: no guarantee of IRS acceptance, OIC is a fit-check only, the coarse tax_account_type is nonidentifying, and brief:true changes the response shape. It does not mention rate limits or the exact output structure, but the added caveats are substantive.

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-loads the triggering scenario before the enumerated paths, which is good structure. It is slightly long and mildly redundant - 'never a promise of acceptance' and 'Never guarantees an IRS outcome' say the same thing - costing it the top score.

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?

With an output schema present, the description need not explain return values, and it covers what matters: the paths screened, the forms surfaced, collection-statute context, privacy of inputs, and the outcome caveat. Nothing an agent needs to call this correctly 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 description coverage is 100%, so every parameter is already fully documented, including the ability_to_pay enum values and the brief flag. The description largely repeats schema content ('Set brief:true for a shorter answer', the nonidentifying tax_account_type) rather than adding syntax or edge-case meaning, so the baseline 3 is appropriate.

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 ('Screens which IRS paths may fit') and enumerates the exact resources it evaluates - short-term payment plan, Simple Payment Plan, installment agreement, Offer in Compromise, Currently Not Collectible, penalty abatement - plus the forms returned. This is far more specific than siblings like triage_tax_problem or estimate_irs_penalty, letting an agent distinguish it without opening the 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?

Gives a clear, concrete triggering context: someone owes back taxes and asks how to settle, get a payment plan, lower the amount, or stop collection. It does not name alternative siblings (e.g. triage_tax_problem, book_consultation) or state when not to use it, so it falls short of a 5.

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 Tools 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.