Skip to main content
Glama

Arc & Ledger Tax Tools

by io.github.Bgenc48

Estimate IRS penalties and interest

estimate_irs_penalty
Read-only

Use this when someone owes the IRS and asks how much the penalties and interest will be, or what late filing/paying costs. Estimates the failure-to-file (5%/mo) and failure-to-pay (0.5%/mo) penalties and interest on a balance, and explains the current Automatic Exemption from Penalty, First Time Abate, and reasonable-cause relief paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
months_lateYesWhole months past the deadline. The failure-to-file penalty counts any part of a month as a full month.
return_filedNoWhether you actually FILED the return (even if you did not pay). If false, the larger 5%/month failure-to-file penalty applies. Defaults to false (not filed).
balance_owed_usdYesThe unpaid tax balance (the tax itself, before penalties and interest).

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which align with the description's estimation nature. The description adds context about specific penalties and relief paths without contradicting annotations.

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, front-loaded with usage guidance, followed by a precise list of what the tool estimates. No extraneous words.

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 simplicity (3 params, has output schema, no nested objects), the description covers when to use, what it estimates, and relief paths. No gaps identified.

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?

Input schema has 100% description coverage, so each parameter is already documented. The description does not add new parameter-level details beyond the schema, meeting the baseline expectation.

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 specifies the verb 'estimate' and the resource 'IRS penalties and interest', and distinguishes from sibling tools like check_resolution_options and decode_irs_notice by focusing on penalty/interest estimation and relief paths.

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 states when to use this tool ('when someone owes the IRS and asks how much the penalties and interest will be') and implies the context (late filing/paying costs). It lacks explicit exclusions or alternatives but provides sufficient context.

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