Skip to main content
Glama

Arc & Ledger Tax Tools

by io.github.Bgenc48

Explain a tax document

explain_tax_document
Read-only

Use this when a user receives a US tax form or information document and wants to know what it is, why they got it, which boxes matter, where it goes on their return, what to double-check, or what to do if it is wrong, duplicated, or never arrived. Covers W-2, W-2G, the 1099 family (NEC, MISC, K, INT, DIV, B, DA, R, G, C, S, SA, Q), Schedule K-1 (partnership 1065, S-corp 1120-S, estate/trust 1041), SSA-1099, 1042-S, 5498, 1098, 1098-T, 1098-E, 1095-A/B/C, and W-9 / W-8BEN requests. For IRS letters and notices (CP or LT codes) use decode_irs_notice instead. Set brief:true for a shorter answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
briefNoSet true for a shorter answer: skips the box-by-box guide and the pre-filing checklist.
documentYesThe tax form or document name as printed on it, e.g. "W-2", "1099-K", "1099-NEC", "Schedule K-1 (Form 1065)", "1042-S", "1098-T", "SSA-1099", "1095-A", "W-9".

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds detail on what the tool covers (box-by-box guide, pre-filing checklist) and the effect of brief=true, providing added behavioral context beyond 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 efficiently conveys scope, usage, and alternatives. While not overly concise, it avoids fluff and front-loads the use case.

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 presence of an output schema, the description sufficiently covers when, what, and how. It lists covered forms, exclusions, and parameter effects, making it complete for an explanation tool.

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 covers 100% with descriptions. Description enriches with concrete examples ('W-2', '1099-K'), max length hint, and explanation of the brief parameter, adding value beyond the schema.

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 explains US tax documents, lists specific forms (W-2, 1099 family, etc.), and distinguishes from sibling tool decode_irs_notice.

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 tells when to use ('when a user receives a US tax form...'), when not to use ('For IRS letters and notices use decode_irs_notice instead'), and mentions the brief parameter for shorter answers.

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