accept_setup_plan
ChatGPTMaterialize a draft setup plan. Workspace plans (setup_workspace) create the selected document types (system types are reused by name), form templates with fields, and the public page. Request plans (plan_request) find or create the client, create a draft request, attach matched items and create the rest; client.email is required. Selections default to everything the judge marked keep; pass explicit candidate id lists to override. Returns what was created plus the PDF slots still pending upload. Only call this after the user has reviewed the plan and explicitly asks to create it.
add_checklist_item
ChatGPTAdd a checklist item (requested document) to an existing request. On a request that has already been sent, the new item appears in the client's portal right away and is included in their reminder emails, so only do that when the user explicitly asks.
add_form_field
ChatGPTAdd a field to an existing form template. The field is appended to the end of the form. A field can be conditionally shown based on an earlier select/radio/checkbox field's answer via config.visibility (use get_form_template to look up the parent field's id). An appointment field lets the client book a time slot. Its config keys: timezone (IANA zone), slot_minutes, buffer_minutes, intervals ({mon..sun: [{from: "09:00", to: "17:00"}]}), blackout_dates (ISO dates), min_notice_hours, rolling_days, appointment_type (one_on_one | group), max_per_slot (group only), max_per_day. Omitted keys use sensible defaults (30-minute slots, weekdays 9-5, 24h notice, 30-day window).
assign_client_to_party
ChatGPTAssign a client to a party that doesn't have one yet. Required before creating a request for the party.
assign_request
ChatGPTAssign a request to a workspace member, or unassign it. The assignee receives the professional-facing notifications for the request. Only call this when the user explicitly asks to reassign it.
assign_upload
ChatGPTAssign an upload to a checklist item on the same request. Use to correct a misfiled upload. The upload becomes classified and the item becomes received; if the item it was moved away from has no uploads left, that item is reset to pending. Both changes show in the client's portal and their reminder emails, so only call this when the user explicitly asks.
attach_form_to_request
ChatGPTAttach a saved form template to a request. The template's fields are snapshotted — future template edits won't affect this request. On a request that has already been sent, the form appears in the client's portal right away, so only do that when the user explicitly asks.
attach_inline_form
ChatGPTBuild a one-off form directly on a request without creating a template. Use this when you need a custom form for a single request. Fields support types: text, textarea, number, date, email, phone, select, radio, checkbox, signature. Appointment fields are not supported on inline forms; put them on a template instead. On a request that has already been sent, the form appears in the client's portal right away, so only do that when the user explicitly asks. Best practices: - Set required: true for fields the client must fill out. - Use config.validation to enforce format, e.g. "email" or "phone_us". - When the field name implies a type (e.g. "Email Address"), prefer the matching field type (email) and add the corresponding validation.
attach_pdf_to_request
ChatGPTAttach a PDF template to a request as a fill request. The client will be prompted to fill in the PDF fields in the portal. On a request that has already been sent, each signer can open and sign it right away, so only do that when the user explicitly asks. Note: The template must have fillable fields (native or custom) for the client to fill out. If it has none, the user should add fields via the editor first. For documents needing multiple signatures (e.g. husband + wife + attorney), pass signers: an ordered list where each entry is either {"client_id": "cl_xxx"} or {"owner": true} (the account owner signs from the dashboard), each with an optional "role_label". Assign signature fields with field_assignments: a map of custom field id -> 0-based signer index. All signers sign in parallel; the final PDF is composed and delivered to everyone once the last signer finishes. The response includes each client signer's signing link.
cancel_request
ChatGPTCancel a document request. Sets its status to "archived", closes the client's portal link immediately, and stops all further reminder emails. No email is sent to the client. Use this for dead requests that will never be fulfilled. Only call this when the user explicitly asks to cancel the request.
complete_request
ChatGPTMark a document request as complete. The client's portal shows the request as complete and their portal link expires after a grace period. No email is sent. Only call this when the user explicitly asks to complete the request.
create_client
ChatGPTCreate a new client. Requires at least a name or email address. Returns the created client.
create_deal
ChatGPTCreate a new deal.
create_deal_from_template
ChatGPTCreate a new deal from a deal template. This creates the deal with all party roles pre-configured from the template. Parties are created without clients — assign clients afterward using update_party.
create_document_copy
ChatGPTCreate a "clean copy" of a photo upload: a derived scanner-style PDF (perspective-corrected and cleaned to black-and-white). The original file is never modified. Available on paid plans, for JPEG or PNG uploads. Generation is asynchronous — the response shows document_copy_status "processing"; fetch the upload again until it is "ready" (document_copy_url is then set) or "failed".
create_form_template
ChatGPTCreate a new form template with fields in one call. Fields support types: text, textarea, number, date, email, phone, select, radio, checkbox, signature, appointment. Fields with options (select, radio, checkbox) need config.options as a list of strings. Appointment fields let the client pick a time slot; see add_form_field for the config shape. Best practices: - Set required: true for fields the client must fill out. - Use config.validation to enforce format, e.g. "email" or "phone_us". - When the field name implies a type (e.g. "Email Address"), prefer the matching field type (email) and add the corresponding validation.
create_party
ChatGPTAdd a party (participant) to a deal. Requires a client_id and role.
create_pdf_upload_url
ChatGPTGet a one-time URL to upload a PDF without base64. PUT the raw PDF bytes to upload_url (Content-Type: application/pdf) within 15 minutes, then call upload_pdf_template with the returned upload_key.
create_public_page
ChatGPTCreate a public page. Attach at least one document type, form template, PDF template, or a fee, otherwise the page shows as unavailable to visitors. Public pages are live-only (not available with test API keys). The page is public as soon as it's created, so only call this when the user explicitly asks to publish it.
create_request
ChatGPTCreate a new document request for a client. Optionally include checklist items and co-clients (additional recipients who each get their own portal link, e.g. a spouse on a joint filing). The request is created in draft status — use send_request to email it to the recipients. Typical workflow: 1. create_request with checklist items (documents to upload) and any co-clients 2. Attach forms (attach_form_to_request or attach_inline_form) and/or PDFs (attach_pdf_to_request) 3. Show the user the draft. Only when they explicitly ask to send: send_request
create_request_from_template
ChatGPTCreate a fully-loaded request for a deal party using the deal template's attachments. The party must have a client assigned and the deal must have been created from a template. Automatically attaches form templates, PDF templates, and document checklists defined for the party's role in the template.
dispatch_deal
ChatGPTOne-call deal creation: upserts clients, creates a deal from a template, assigns clients to parties, generates requests, and optionally sends them. Returns the full deal with portal URLs. Only set auto_send when the user explicitly asks to send; otherwise the requests stay drafts.
find_or_create_client
ChatGPTFind a client by external_id+external_source, or by email. If not found, create one. Returns the client and whether it was created or updated.
find_pdf_text
ChatGPTSearch a PDF template's text and return where each match sits: {page, x, y, w, h} in PDF points from the page's top-left corner, plus the full line it's on. Use it to find signature labels (e.g. "Signature of Debtor") before placing fields with set_pdf_fields. Matching is case-insensitive within one line. Scanned PDFs without a text layer return no matches; place by coordinates instead.
get_appointment
ChatGPTGet one appointment by ID, with its request and client.
get_deal
ChatGPTGet a single deal by ID, including all parties and their requests.
get_deal_template
ChatGPTGet a deal template with all party roles and their attachments (form templates, PDF templates, document types). Use this to inspect what a template includes before creating a deal from it.
get_form_responses
ChatGPTGet form responses for a request. Returns all attached forms with their fields and submitted responses (if completed).
get_form_template
ChatGPTGet a form template with all its field definitions. Use this to inspect a template before attaching it to a request.
get_pdf_fill
ChatGPTStatus of a PDF signature (fill request): overall status, each signer's status and signed_at, signing links for anyone still pending (the owner's link opens the dashboard, where they sign themselves), and once completed a download_url for the final signed PDF with its Certificate of Completion appended. The download URL needs no login and expires after 24 hours (call get_pdf_fill again for a fresh one), so treat it like the document itself.
get_pdf_fill_signatures
ChatGPTReturn the audit trail for a completed PDF fill request: per-signature field name, SHA-256 hash, IP address, user agent, and signed-at timestamp. These are the same records that appear on the Certificate of Completion page appended to every signed PDF.
get_pdf_template
ChatGPTGet a PDF template with field definitions and editor URL. Use this to inspect a template before attaching it to a request.
get_public_page
ChatGPTGet a public page with its attachments, fee, and submission count.
get_request
ChatGPTGet a single document request by ID. Includes full detail with items, forms, the portal_url the primary client uses to upload documents, and a recipients array with each co-client's own portal_url.
list_appointments
ChatGPTList appointments booked through appointment form fields, ordered by start time. Filter by a date window, status, client, or request. Times are UTC ISO 8601; timezone is the zone the client booked in. Paginate with after (the last appointment's id) while has_more is true.
list_clients
ChatGPTList all clients for the authenticated user. Optionally filter by search term (matches name or email).
list_deal_templates
ChatGPTList all deal templates (user-created and system templates). Deal templates define multi-party workflows with pre-configured roles, forms, PDFs, and document checklists for each party.
list_deals
ChatGPTList all deals. Optionally filter by status.
list_form_templates
ChatGPTList all saved form templates for the authenticated user. Returns template summaries with field counts.
list_members
ChatGPTList the people in this workspace who can be assigned requests and deals. Returns each member's id (mem_…), role, name, and email.
list_pdf_templates
ChatGPTList all PDF templates for the authenticated user. Returns template summaries with field counts and page info.
list_public_pages
ChatGPTList public pages: reusable shareable links (/i/:slug) anyone can open to upload documents, fill forms, sign PDFs, or pay a fee. Each submission creates a client and a sent request. Includes the public URL and submission count for each page.
list_request_reminders
ChatGPTList the reminder audit trail for a request. Shows when each reminder was sent, to whom, with what urgency, and which items were pending. recipient_type is client, co_client, professional_overdue, professional_cap_reached, professional_never_viewed (no portal view 3 days after sending), or professional_due_passed (due date went by, reminders stopped).
list_requests
ChatGPTList document requests. Optionally filter by status, client_id, or deal_id. Each request includes a recipients array with any co-clients' portal URLs.
list_uploads
ChatGPTList all uploads for a document request.
plan_request
ChatGPTDraft one request from a plain-English description of what you need from a client ("send Jane my questionnaire, two years of tax returns, and the fee agreement"). Candidates are matched against your existing document types, form templates and PDF templates; a confident match is reported under match and will be reused on accept, everything else is created. Client name/email are extracted when present. Nothing is created until accept_setup_plan is called.
preview_pdf_template
ChatGPTRender template pages as images with each custom field drawn as a bracketed label (e.g. "[Debtor signature]") at its position, to check placement after set_pdf_fields. Returns up to 5 pages per call (default "1-5").
re_request_item
ChatGPTRe-request a checklist item. Resets status to pending and clears review_status; the review_note is kept, shown to the client on the portal, and emailed to them. Previous uploads are kept for reference but marked superseded and excluded from exports. Use this when a submitted document was rejected and the client needs to resubmit. Only call this when the user explicitly asks to re-request the item.
request_signatures
ChatGPTOne-off signature request: creates a DRAFT request whose only item is this PDF, for documents like a lender's agreement that don't need a document checklist. The first client signer is the request's client; other client signers are added as co-clients so they get the portal email and reminders. Place fields first (set_pdf_fields) and assign them per signer with field_assignments (field id -> 0-based signer index). Example: signers [{"client_id": "cl_debtor", "role_label": "Debtor"}, {"client_id": "cl_joint", "role_label": "Joint Debtor"}, {"owner": true, "role_label": "Attorney"}], signing_order "sequential". Nothing is emailed. Call send_request with the returned request_id only when the user explicitly asks to send. Track progress with get_pdf_fill.
send_request
ChatGPTSend a document request to the client. Changes status from draft to sent. By default sends an email to the client with the portal link. Set skip_email to true to activate the request without sending an email (useful when you want to share the portal link manually, e.g. via text message). Only call this when the user explicitly asks to send this request. Creating or editing a draft is never permission to send: show the draft and ask first.
set_pdf_fields
ChatGPTPlace signature, initials, date, text or checkbox fields on a PDF template without the visual editor. Each field is placed either: - by text anchor: {"type": "signature", "label": "Debtor signature", "anchor": {"text": "Signature of Debtor", "position": "above"}} position is above (default; most forms print the label under the line), below, left or right. Optional: occurrence (1-based, when the text appears more than once), page (limit the search), offset_x/offset_y, w, h. - or by coordinates: {"type": "date", "page": 3, "x": 380, "y": 640} (PDF points, top-left origin; w/h optional). Sizes default to the editor's (signature 200x50). signature/initials default to required. mode "replace" (default) replaces all custom fields (refused while a signature request using the template is in progress); "append" adds to them. Nothing is saved if any field can't be placed; the error says which and, for a missing anchor, lists nearby lines. Returns the placed fields with their ids: pass those ids in attach_pdf_to_request's field_assignments to give each signer only their own fields. Check placement with preview_pdf_template.
setup_workspace
ChatGPTBuild a workspace proposal from a plain-English description of the business and what it needs from clients. Returns a draft plan: document types clients upload, intake forms with fields, a public start page, and the PDFs the owner must supply (engagement letter, consents). Each item carries a verdict (keep / unsure / drop) and the raw judgment probabilities. Nothing is created until accept_setup_plan is called. Live-only.
update_client
ChatGPTUpdate an existing client's name, email, or phone. Returns the updated client.
update_item
ChatGPTUpdate the review status and optional note on a checklist item. Only works when the item's status is "received" (i.e., the client has uploaded). Valid review statuses depend on the user's settings (defaults: in_review, approved, rejected). The status and note are shown to the client in their portal, so only set them when the user explicitly asks.
update_public_page
ChatGPTUpdate a public page. Attachment id lists, when given, replace that kind entirely; omitted kinds are left unchanged. Set active=false to take the page down. Changes are public immediately, so only call this when the user explicitly asks.
update_request
ChatGPTUpdate a document request's title, description, due date, assignee, or reminder settings. On a sent request, enabling reminders or extending the due date resumes automatic reminder emails to the client, so only change those when the user explicitly asks.
upload_pdf_template
ChatGPTUpload a PDF file as a new template. The PDF is analyzed for page count and native form fields (AcroForm). Send the file content as base64 since MCP uses JSON-RPC. If the PDF has native fillable fields, it can be attached to a request immediately. If the PDF has NO native fields, the user must add fields in the visual editor before attaching it — the response will include an editor_url for this.
upload_to_item
ChatGPTUpload a document file directly onto a checklist item on the firm's behalf — e.g. when a client emailed the document instead of using the portal. The file is attached to the item and the item becomes received, so reminders for it stop and the client's portal shows it as received. Only call this when the user explicitly asks to upload the file. Send the file content as base64 since MCP uses JSON-RPC. Accepted content: PDF or image, max 10 MB.