Skip to main content
Glama

Arc & Ledger Tax Tools

by io.github.Bgenc48

Check US withholding and treaty rates (W-8BEN)

check_treaty_withholding
Read-only

Use this when a non-US person or company receiving US-source income (dividends, interest, royalties, freelance/personal services, or a scholarship) asks how much US tax will be withheld, whether a tax treaty reduces it, or which form to give the payer (W-8BEN, W-8BEN-E, W-9, Form 8233). Returns the default statutory rate, the US-Turkey treaty rate where one applies, the documentation a treaty claim needs (including a TIN/ITIN), and how refunds of over-withholding work.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payee_typeNoWhether the payee is an individual or a company/entity. Defaults to individual. Determines the form (W-8BEN vs W-8BEN-E) and the treaty dividend rate.
income_typeYesThe kind of US-source payment: "dividends" (from US stocks or a US corporation), "interest", "royalties" (software, content, IP licensing), "personal_services" (freelance/consulting work or wages), or "scholarship_fellowship".
payee_countryYesCountry of TAX RESIDENCE of the person or company RECEIVING the payment. "turkey" returns the US-Turkey treaty rates this server carries; "other_non_us" returns the default statutory rates and how to check your own treaty; "united_states" covers US persons (who use Form W-9, not a treaty claim).

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

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

Annotations already indicate readOnlyHint=true. The description adds value beyond annotations by explaining the tool's output: default rate, treaty rate, documentation needed, and refund process. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph that is concise and front-loaded with key usage context. It could be slightly more structured but remains clear and efficient.

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 complexity (3 parameters, all with enums, output schema present), the description covers all necessary aspects: when to use, what returns, and parameter context. It is fully adequate.

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%, so the description's additional detail on forms (W-8BEN, W-8BEN-E, etc.) is helpful but not essential. It adds marginal value over the schema's parameter descriptions.

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 that the tool checks US withholding and treaty rates for non-US persons receiving US-source income. It specifies the income types and output details, and distinguishes it from sibling tools which cover different tax topics.

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 explicit context for when to use: when a non-US person or company asks about withholding, treaty rates, or forms. It lists income types covered. While it does not explicitly list when not to use or mention alternatives, the sibling tool list provides that 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