Skip to main content
Glama

Arc & Ledger Tax Tools

by io.github.Bgenc48

Decode an IRS notice

decode_irs_notice
Read-only

Use this when a user mentions receiving an IRS or state tax letter or notice and wants to know what it means, the deadline, or what to do. Give it the notice code (e.g. CP2000, CP14, LT11) and optionally the notice date and amount shown. Set brief:true for a shorter answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
briefNoSet true for a shorter answer: skips the generic how-to-read guidance and common-error list.
notice_codeYesThe notice or letter code printed on the IRS mail, e.g. "CP2000", "CP 14", "LT11", "Letter 1058".
amount_shownNoThe dollar amount the notice proposes or bills, if any. Optional; used only for context, never stored.
received_dateNoDate on the notice (YYYY-MM-DD). Used to compute the response deadline. The IRS clock runs from the notice date printed on the letter.

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.8/5.0
Behavior5/5

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

Discloses important behaviors: amount_shown is 'never stored', received_date computes response deadline, brief flag skips generic guidance. Annotations (readOnlyHint=true, destructiveHint=false) are consistent and enhanced by these details.

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, no wasted words. Front-loaded with purpose and usage, followed by parameter guidance. Efficient and scannable.

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?

Covers purpose, when to use, parameter semantics, and behavioral details. Output schema exists, so return value description is unnecessary. No gaps given the tool's simplicity.

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?

Adds meaning beyond schema descriptions: explains brief effect, received_date usage for deadline, amount_shown used for context only, notice_code includes examples. Schema coverage is 100%, but description enriches understanding.

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 the tool decodes IRS/state tax notices, specifying the trigger (user mentioning a notice) and the output (meaning, deadline, action). This distinguishes it from sibling tools like 'estimate_irs_penalty' 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 Guidelines4/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 mentions receiving an IRS or state tax letter or notice') and what parameters to provide (notice code, optional date/amount, brief flag). Lacks explicit 'when not to use' but context with siblings makes it largely clear.

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