Aiwyn Tax
One of the ways to connect Aiwyn Tax
Automate tax workflow tasks and manage client engagements. Track deadlines, organize documents, and handle billing for accounting firms.
- Version:
- hosted
Install
Generated from the server’s transport data — never hand-written. Placeholders in angle brackets are yours to fill.
Run it with its own identity, a budget you set, and every call audited — no local config to keep in sync.
Add to a connect0 projectYou will sign in first, then land back on this page.
What it can do
As declared by the publisher
Tools · 10
calculate_taxCalculate a tax return for a given jurisdiction. The 'input' argument must conform to the JSON schema returned by the tax\_namespace\_schema tool. Returns computed tax return document on success, or validation errors if the input is invalid. If some inputs trigger a PARTIAL DISQUALIFICATION, the document is still returned for the supported fields; review the disqualification details and estimate the impact of the unsupported fields on the taxpayer's tax owed or refund due. Use the check\_tax tool first to validate the input before calculating the tax return with this tool.IMPORTANT RULES: (1) All field values must be wrapped as {"value": } — never pass bare values. (2) Currency amounts are whole-dollar integers (e.g. $19,312.42 = 19312). (3) Every item in an array namespace (NamespaceList) must have a "uuid" field with a valid UUIDv4 string. UUIDv4 format: xxxxxxxx-xxxx-4xxx-\[89ab]xxx-xxxxxxxxxxxx — the 3rd group MUST start with '4' (version) and the 4th group MUST start with '8', '9', 'a', or 'b' (variant). NEVER construct UUIDs manually (e.g. 'B1111111-1111-1111-1111-111111111111' is invalid). Use a UUID generator; example valid value: 'a3b4c5d6-e7f8-4a9b-8c0d-1e2f3a4b5c6d'. (4) Nested arrays (e.g. w2\_state\_local\_tax\_grp inside a w2) also require a UUIDv4 on each item. (5) Use "who\_applies\_to" to cross-reference entries: {"value": "taxpayer"} for singletons, {"value": "#"} for array items (e.g. "dependent\_detail#"). Other named reference fields (e.g. "person" in qualifying\_person\_grp, "student" in student\_educational\_instn\_grp) use the same "#" format. (6) For state returns with Extended Links (state namespace extending a federal NamespaceList), each extended link item must use a UUIDv5 generated from the source item's UUID (as the namespace) and the extended namespace name (as the name). Matching is UUID-based, not positional. The number of expected instances depends on the source formula — it is NOT always a 1:1 match with the federal list (e.g. CA Form 3853 ca\_household\_grp expects taxpayer + spouse + all dependents). Incorrect or random UUIDs cause SILENT DATA LOSS — the server drops unrecognized UUIDs and replaces them with empty instances. Use the generate\_uuid\_v5 tool with the source item's UUID as the source\_uuid and the extended namespace name (e.g. "ca\_provider", "ca\_irsw2\_g") as the namespace input.Example: generate\_uuid\_v5(source\_uuid: w2\_uuid, namespace: "ca\_irsw2\_g") for a CA W-2 extension.(7) return\_header is top-level, NOT nested inside return\_data. Use tax\_simple\_return first to see the full input structure and examples.
check_taxCheck inputs to calculate a tax return for a given jurisdiction. The 'input' argument must conform to the JSON schema returned by the tax\_namespace\_schema tool. Returns 'Success' on success, or validation errors if the input is invalid. If some inputs trigger a PARTIAL DISQUALIFICATION, the check still succeeds but includes disqualification details — proceed to calculate\_tax to get the document and estimate the impact. Use this tool to validate inputs before calculating the tax return.
generate_tax_pdf_toolStart async PDF generation for a tax return. The 'input' argument must conform to the JSON schema returned by the tax\_namespace\_schema tool. Returns a job ID to poll with get\_tax\_pdf.Use the check\_tax tool first to validate the input before generating the tax PDF with this tool.The input follows the same rules as calculate\_tax: all values wrapped as {"value": }, array items require UUIDv4 fields (extended link items use UUIDv5), references use who\_applies\_to, and return\_header is top-level (not inside return\_data). Use tax\_simple\_return to see the full input structure.
generate_uuid_v5Generate a UUID v5 based on a source uuid and namespace.
get_tax_pdf_toolCheck status of a PDF generation job. Returns the status and a download URL when completed, only use this tool after generating the tax PDF with the generate\_tax\_pdf tool and it successfully returns a job ID.
tax_jurisdictionsList all supported tax jurisdictions for a given tax year.
tax_namespacesList all available input namespaces for a given jurisdiction. Use the returned names with the tax\_namespace\_schema tool to get the schema for a specific namespace. Requires a jurisdiction (e.g. "us" for federal, "ca" for California). Use the tax\_jurisdictions tool first to discover available jurisdictions. NAMESPACE NAMING CONVENTIONS: Federal namespaces: irs1040, irs1040\_schedule1, irs8962, w2, dependent\_detail, etc. State namespaces: always prefixed with the state abbreviation (ca\_form540, ny\_it201, az\_form140). NAMESPACE TYPES: Some namespaces are singletons (object), others are NamespaceLists (array) that can hold multiple items — e.g. w2 (multiple W-2s), dependent\_detail (multiple dependents), irs1040\_schedulec (multiple businesses). NamespaceList items require UUIDv4 fields. State NamespaceLists may act as Extended Links that extend a federal NamespaceList (e.g. ca\_provider extends care\_provider\_grp). Extended link items must use UUIDv5 (deterministic, derived from source item UUID as namespace + extended namespace name as name). Matching is UUID-based, not positional. Wrong UUIDs cause silent data loss.Use the generate\_uuid\_v5 tool with the source item's UUID as the source\_uuid and the extended namespace name (e.g. "ca\_provider", "ca\_irsw2\_g") as the namespace input.Example: generate\_uuid\_v5(source\_uuid: w2\_uuid, namespace: "ca\_irsw2\_g") for a CA W-2 extension.
tax_namespace_schemaGet the TCB input schema for a single namespace (e.g. "irs1040", "irs1040\_schedulec", "ca\_form540"). Returns the properties and types for that namespace. HOW TO READ THE SCHEMA: (1) Each field references a type like tcb\_string\_null, tcb\_integer\_null, or tcb\_boolean\_null. All values must be wrapped as {"value": }. (2) If the namespace title ends in '\_list' (e.g. 'w2\_list', 'dependent\_detail\_list'), it is a NamespaceList — an array of objects. Each array item MUST include a "uuid" field (non-null UUIDv4 string). (3) Reference fields link entries to other namespaces e.g. "person" in qualifying\_person\_grp, "student" in student\_educational\_instn\_grp. All use the same format: {"value": "#"} (e.g. "dependent\_detail#"). (4) Nested arrays within a namespace (e.g. w2\_state\_local\_tax\_grp inside w2) also require uuid on each nested item. (5) Pattern-validated strings (e.g. SSNs, ZIPs, dates) have regex constraints in the schema $defs. SSNs/EINs: 9-digit string (no dashes). ZIPs: 5 or 9 digits. Dates: YYYY-MM-DD.
tax_simple_returnCall this FIRST when beginning any tax return. Returns the curated namespace list, top-level structure guide, example input, and step-by-step filing workflow. By default returns a simple scenario (single or MFJ filer, W-2 income only, standard deduction, no dependents). Pass scenario="with\_dependents" for returns that include dependents, child care (Form 2441), and education credits (Form 8863). Optionally pass a state jurisdiction (e.g. "ca") to also include state-level namespaces — if you don't know which state applies, ask the user before calling.
tax_yearsList all supported tax years.