Skip to main content
Glama

Arc & Ledger Tax Tools

by io.github.Bgenc48

Triage a tax problem

triage_tax_problem
Read-only

Use this when someone has a tax problem and does not know where to start; call it FIRST, before the specific tools. Covers an IRS or state letter, back taxes they cannot pay, unfiled years, a levy or wage garnishment, an audit, penalties, an identity-verification letter, and payroll tax trouble. Returns an urgency level, a this-week and this-month action plan, what not to do, which tool to run next for the specifics, and the matching published-fee service. General information only; never a guaranteed IRS outcome. Set brief:true for a shorter answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
briefNoSet true for a shorter answer: urgency, this-week actions, and the matching service only.
problemYesThe tax problem, as close as it maps. irs_notice = any IRS or state letter; back_taxes_owed = a balance that cannot be paid in full; unfiled_returns = one or more years never filed; levy_or_garnishment = a bank levy, wage garnishment, or a final intent-to-levy letter; audit_or_exam = an IRS audit or examination letter; penalties = penalty charges on an account; identity_verification = a 5071C/4883C identity letter or suspected refund identity theft; payroll_tax_941 = unpaid or late employer payroll taxes; state_tax = a state tax agency problem; not_sure = anything else.
amount_bandNoRoughly how much is at stake, if known. Bands only, never an exact figure. Current IRS Simple Payment Plan balance criteria generally use a $50,000 ceiling for eligible individual and non-trust-fund accounts and a $25,000 ceiling for eligible business trust-fund accounts.
years_behindNoFor unfiled returns: how many years are unfiled. The IRS generally looks for the last six years filed to restore filing compliance.
has_deadline_soonNoTrue if a letter shows a response or payment date within about two weeks. Raises the urgency. No dates are computed here; use decode_irs_notice for exact deadline math.

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_urlYesThe arcandledger.com page that backs this answer.
server_versionNoServer release that produced this response (matches GET /version).

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, set to false destructive and open-world. The description adds value by disclosing the tool returns an urgency level, action plans, what not to do, the next tool, and a fee service, plus the disclaimer 'General information only; never a guaranteed IRS outcome.' No contradiction with annotations.

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?

The description is a single, dense paragraph that covers all key points. It is mostly concise, though the list of covered problems could be integrated more tightly. Still, every sentence adds value.

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?

Given the tool's complexity (triage, multiple problem types, output schema exists), the description fully informs the agent: when to use, what parameters do, what the output includes, and limitations. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description enriches parameters by explaining how 'brief:true' truncates the answer and giving context for 'has_deadline_soon' (raises urgency, no date math here). It also maps enum values to real-world scenarios, aiding selection.

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 starts with a specific verb-resource pair ('triage a tax problem') and immediately states usage priority: 'call it FIRST, before the specific tools.' It lists covered problem categories, clearly distinguishing it from sibling tools like 'decode_irs_notice' or 'check_resolution_options.'

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

Usage Guidelines5/5

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

Explicitly says 'Use this when someone has a tax problem and does not know where to start' and 'call it FIRST, before the specific tools,' implying it's the initial triage tool. It describes what it returns (urgency, action plans, next tool) and that it provides general information, not guaranteed outcomes.

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 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
Disambiguation4/5

Most tools have distinct purposes (e.g., FBAR/FATCA, penalty estimation, consultation booking), though check_resolution_options and estimate_irs_penalty both deal with IRS debts but address different aspects (settlement paths vs. penalty calculation). Overall, boundaries are clear due to detailed descriptions.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., book_consultation, check_fbar_fatca, estimate_reasonable_comp). No mixing of styles or vague verbs.

Tool Count4/5

18 tools is slightly on the high side but justified for a comprehensive tax tool covering common scenarios (penalties, estimates, notices, formations). Each tool serves a specific need without redundancy.

Completeness4/5

The set covers major tax areas (foreign reporting, penalties, estimated taxes, entity formation, IRS notices). Minor gaps exist, such as state income tax and retirement contributions, but the core domain for small business owners and non-residents is well covered.

Resources