Skip to main content
Glama

Arc & Ledger Tax Reference

by com.arcandledger

Estimate accountable-plan reimbursements

estimate_accountable_plan
Read-only

Use to estimate potentially reimbursable business expenses under an accountable-plan scenario, including the split 2026 business-mileage rates. The result does not establish a plan or determine substantiation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
business_milesNoBusiness miles driven in your personal vehicle. For 2026, also identify whether the miles were before July 1, on or after July 1, or span both periods because the IRS changed the rate midyear.
cell_internet_usdNoAnnual business-use portion of your cell phone and home internet.
marginal_tax_rate_pctNoYour combined marginal tax rate as a percent (e.g. 24, or 33 to include state). Used to estimate the tax saving. Defaults to 22.
business_mileage_periodNoWhen the business miles occurred. Defaults to mixed_or_unknown, which returns a reimbursement range rather than inventing a single rate. For miles in both 2026 periods, call the tool once per period and add the results.
home_office_expense_usdNoAnnual business-use portion of your home costs (rent/mortgage interest, utilities, insurance x business-use %). If you only know square footage, use the simplified method: $5/sq ft up to 300 sq ft = $1,500 max.
other_business_expense_usdNoOther out-of-pocket business expenses you personally paid (supplies, travel, professional dues, etc.).

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

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

The description adds value beyond annotations by stating that the result does not establish a plan or determine substantiation, and that for mixed periods it returns a range rather than a single rate. Annotations already declare readOnlyHint=true, so the description reinforces the non-destructive nature with important caveats.

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, immediately front-loaded with purpose. Every sentence adds essential context. No redundant or verbose phrasing.

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 complexity of 6 parameters, full schema documentation, and an existing output schema, the description sufficiently covers the tool's scope, limitations, and usage notes. It tells the agent what the result does and does not accomplish.

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?

Schema description coverage is 100%, so baseline is 3. The tool description does not add new information about parameters beyond what is already in the input schema. The schema itself provides detailed descriptions for each parameter, so the description carries no extra semantic load.

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's purpose: 'estimate potentially reimbursable business expenses under an accountable-plan scenario' and mentions the specific 'split 2026 business-mileage rates'. This distinguishes it from sibling tools like estimate_augusta_rule or estimate_quarterly_taxes.

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 says 'Use to estimate...' and explicitly notes that 'The result does not establish a plan or determine substantiation.' It also advises to call the tool once per period for mixed mileage. However, it lacks explicit guidance on when to use alternatives among sibling estimate tools.

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