Skip to main content
Glama

Arc & Ledger Tax Tools

by io.github.Bgenc48

Check FBAR and FATCA obligations

check_fbar_fatca
Read-only

Use this when a user has foreign bank accounts, assets, or unfiled foreign-account reports and needs to know their US reporting obligations (FBAR / FinCEN 114 and Form 8938 / FATCA), thresholds, penalty exposure, and catch-up options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lives_abroadYesTrue if your tax home is outside the United States (higher Form 8938 thresholds apply).
account_countNoNumber of foreign accounts, if known.
filing_statusYesYour US tax filing status.
unfiled_yearsNoHow many past years of FBARs you have NOT filed but should have. 0 or omitted if current.
max_aggregate_foreign_balance_usdYesThe highest combined value of ALL your foreign financial accounts at any point during the year, in USD.

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

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

Annotations already declare readOnlyHint=true. The description adds behavioral context by stating the tool checks obligations, thresholds, and penalties, confirming it is non-destructive. No contradictions.

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?

A single, well-structured sentence that front-loads the use case and packs all necessary information efficiently without waste.

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 FBAR/FATCA, the description covers when to use, what is checked (thresholds, penalties, catch-up), and implies the output will inform obligations. With output schema present, this is complete.

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 coverage is 100% with each parameter described. The tool description adds minimal extra meaning beyond the schema, meeting the baseline for full coverage.

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 is for checking US reporting obligations (FBAR/FATCA) for foreign accounts, with specifics on thresholds, penalties, and catch-up options. It distinctively targets foreign account issues, differentiating from sibling tools like check_5472_obligation.

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 starts with 'Use this when a user has foreign bank accounts...' providing clear usage context. However, it does not explicitly mention when not to use or compare to alternatives, leaving some room for improvement.

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