Skip to main content
Glama

Arc & Ledger Tax Reference

by com.arcandledger

Estimate IRS penalties and interest

estimate_irs_penalty
Read-only

Use to estimate selected federal failure-to-file, failure-to-pay, and underpayment amounts from nonidentifying figures. The result is an estimate and does not replace an IRS account transcript.

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_urlYesOfficial IRS or FinCEN authority to review before relying on the result.
server_versionNoServer release that produced this response (matches GET /version).

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe read-only behavior. The description adds no additional behavioral traits beyond confirming it's an estimate. While consistent, it does not disclose extra details like data usage or limitations.

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 with no wasted words: the first states the core action, and the second provides a crucial caveat. It is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only 3 parameters, 100% schema coverage, and an output schema, the description is sufficient. It covers the purpose and limitation without needing to detail return values. Slightly more context about when to use this estimate versus an actual transcript could improve completeness.

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 coverage is 100%, and the description does not add parameter-specific meaning beyond what the schema already provides. The schema describes 'months_late' with rounding behavior and 'return_filed' defaults, so the description adds no additional value for parameters.

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 explicitly states the tool estimates 'federal failure-to-file, failure-to-pay, and underpayment amounts from nonidentifying figures,' clearly specifying the verb (estimate) and resources (penalties and interest). It distinguishes from siblings like 'check_*' or 'estimate_quarterly_taxes' by focusing on penalty calculation.

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 provides clear context by stating the result is an estimate and does not replace an IRS transcript, setting expectations. However, it does not explicitly list when to use this tool versus other estimate tools (e.g., 'estimate_quarterly_taxes') or when not to use it.

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 Reference 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
Disambiguation5/5

Each tool addresses a distinct tax topic or action, such as screening obligations, checking eligibility, estimating amounts, or explaining documents. There is no overlap in purpose, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun or verb_phrase pattern (e.g., check_*, estimate_*, explain_*, decode_*, deadline_calendar). The naming is predictable and clear across the set.

Tool Count5/5

With 13 tools, the server covers a broad range of tax reference needs without being overwhelming. Each tool has a clear purpose and the count is well-suited for the domain.

Completeness4/5

The tools cover common tax reference tasks like screening obligations, estimating penalties, explaining forms, and checking deadlines. A minor gap is the lack of a general tax liability estimator, but overall the set is comprehensive for its stated purpose.

Resources