Arc & Ledger Tax Tools

Get a document checklist

get_document_checklist

Read-only

Use this when someone asks what documents, statements, or records to gather for a US tax filing or engagement: an individual return, a self-employed Schedule C return, a foreign-owned single-member LLC (Form 5472) filing, an S-corp or partnership return, an FBAR/Streamlined offshore catch-up, or an ITIN application. Returns the service-specific document list, first-year onboarding extras, and how to prepare files safely without implying that intake or uploads have opened.

Input Schema

TableJSON Schema

Name	Required	Description
`service`	Yes	What the documents are for: "individual_return" (Form 1040), "self_employed_return" (1040 with Schedule C), "foreign_owned_llc_5472" (pro-forma 1120 + Form 5472 for a foreign-owned single-member US LLC), "s_corp_return" (Form 1120-S), "partnership_return" (Form 1065), "fbar_streamlined_catchup" (late FBARs / Streamlined offshore procedures), or "itin_application" (Form W-7).
`language`	No	Language for an availability or waitlist handoff: English (en), Turkish (tr), or Spanish (es).
`first_year_client`	No	Whether this is your first year working with the firm. Adds the one-time onboarding documents (prior returns, IDs, authorizations).

Output Schema

TableJSON Schema

Name	Required	Description
`relay`	Yes	Instruction to the calling assistant: relay figures and dates verbatim (identical on every response).
`next_step`	Yes	A single review link appropriate to this server surface.
`disclaimer`	Yes	General-information disclaimer (identical on every response).
`source_url`	Yes	The arcandledger.com page that backs this answer.
`server_version`	No	Server release that produced this response (matches GET /version).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 11, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "Language for an availability or waitlist handoff: English (en), Turkish (tr), or Spanish (es).",
+  "enum": [
+    "en",
+    "tr",
+    "es"
+  ],
+  "type": "string"
+}

Changed1 schema field changedJul 26, 2026

changedOutput schema / properties / next_step / description

Previous value: -"A single human handoff to the firm."New value: +"A single review link appropriate to this server surface."

AddedJul 13, 2026

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, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds meaningful context by disclosing that it returns first-year onboarding extras and that it explicitly does not imply intake or uploads have opened — a useful boundary the annotations don't convey. Return-shape detail is covered by the output schema.

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?

Front-loaded with the trigger condition and the enumerated service types; the final clause about intake/upload boundaries is well-placed. The service enumeration is somewhat long but earns its place by matching the enum surface.

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?

With readOnly annotations and an output schema present, the description focuses correctly on selection context and behavioral boundaries. It covers the trigger, the scope, and the 'no implied intake' caveat, leaving only sibling routing unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value by enumerating the service categories in natural language (individual return, Schedule C, Form 5472, S-corp, partnership, FBAR/Streamlined, ITIN) that map to the enum values, reinforcing selection. It doesn't add syntax beyond the schema, so not a 5.

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?

States a specific verb (get/returns) and resource (service-specific document checklist) with concrete scope: the seven filing types it covers. An agent can distinguish this from siblings like explain_tax_document or check_5472_obligation without opening the schema.

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?

Opens with a clear when-to-use trigger ('when someone asks what documents... to gather') and lists the qualifying scenarios. It does not, however, name sibling alternatives or state when not to use it (e.g. versus explain_tax_document), which holds it below 5.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.