Skip to main content
Glama

Arc & Ledger Tax Tools

by io.github.Bgenc48

US filing deadlines for founders

deadline_calendar
Read-only

Use this when a US business owner or nonresident (especially a foreign founder of a US LLC or C-corp) asks what US forms they must file and when. Returns each required federal form, its due date and extension, and the penalty for missing it, including Form 5472, FBAR, and the BOI report. Especially useful for non-US founders of US companies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_typeYesYour US tax entity. foreign_owned_llc = a SINGLE-MEMBER US LLC owned by a non-US person (files pro-forma 1120 + 5472); a multi-member foreign-owned LLC is a partnership, use multi_member_llc. foreign_owned_c_corp = a US C-corp with foreign owners. nonresident_individual = a person filing Form 1040-NR.
filing_yearNoThe tax year whose deadlines you want (the year being reported). Defaults to the prior calendar year.
formed_in_usNoWhether the entity was formed in the US (relevant to the BOI report, from which most US-formed companies are now exempt).
has_us_source_wagesNoNonresident individuals only: whether you had US wages subject to withholding. Determines the 1040-NR due date (April 15 if yes, June 15 if no).
has_foreign_bank_over_10kNoWhether the aggregate of your foreign financial accounts exceeded $10,000 at any point (triggers FBAR).

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

A3.8/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true, so the description does not need to cover safety. It adds that the tool returns due dates, extensions, and penalties, but does not elaborate on data source, update frequency, or behavior beyond what the schema implies.

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?

The description is three sentences, front-loaded with the usage scenario, and contains no filler. Every sentence adds value efficiently.

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 5 parameters, required one, and an output schema, the description is fairly complete. It specifies target audience, included forms, and output type. It could explicitly note that it covers only federal forms, but that is implied.

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% and parameter descriptions are detailed. The tool description does not add new meaning about the parameters themselves; it focuses on output. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns federal form deadlines and penalties for US business owners/nonresidents, mentioning specific forms like 5472, FBAR, and BOI. It distinguishes from sibling tools that focus on single forms, but could more explicitly exclude state or non-federal requirements.

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 tells when to use it ('when a US business owner...asks what US forms they must file and when') and provides context about non-US founders. It does not give explicit when-not-to-use or alternative tools, but the context of sibling tools implies scope limitation.

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