attach_submission_file
ChatGPTAttaches a file to a file field in an existing draft submission. The server downloads the file from a public URL. When to Use: - Adding/replacing file attachments (file fields not supported in create_submission), when you have a public URL for the file - If you have no public URL (for example the file is a chat upload or a local file), do NOT send its content. Give the user the ResumeUrl from create_submission: they upload the file on the draft page in Smarter Drafter, then you call submit_submission. Prerequisites: - Submission must exist as a draft (use submissionId from create_submission with IsDraft=true) - Field ref must match a File field from get_fields_by_form Parameters: - submissionId: The GUID returned by create_submission - fieldRef: The field reference string from get_fields_by_form (e.g., "20001245") - appendFile: true to add to existing files, false to replace all files - file: - FileUrl: A publicly accessible http(s) URL to the file. The server will download this URL — do NOT send base64 or file contents. - FileName: The desired filename including extension (e.g. 'lease.pdf'). - ContentType: Optional MIME type. Inferred from headers if omitted. Response: - Success=true: File attached successfully - Success=false: Returns ErrorMessage with validation details and SuggestedAction Common Errors: - "Field not found": fieldRef doesn't match any field in the form - "Submission not found": Invalid submissionId - "FileUrl must be an absolute http or https URL": the URL is not a public http(s) address - Validation errors: too many files, or the file is too large for the field After Attaching Files: - Call submit_submission when all answers are complete
create_submission
ChatGPTCreates a form submission and initiates document generation (DOCX, EML, PDF). Done only when the user has the files: when IsDraft=false, the task is complete only when the user can open or save every generated file (DOCX, EML when present, PDF). Delivered means the user sees each file as a file they can download in your reply, or you saved it with a tool that writes to the user's own computer, where they can open it. A sandbox or workspace that only you can see is not the user's computer. If your client has a separate step to present or output files, you MUST call it. Saving a file somewhere, or adding it to the conversation as context, reference material or an uploaded document, does NOT deliver it. Prerequisites: 1. Call search_forms to find the form ID 2. Call get_fields_by_form to retrieve field definitions and references (refs) 3. Prepare answers using the field refs as keys Parameters (all nested inside the required mcpRequest object): - mcpRequest.FormId: The form identifier from search_forms - mcpRequest.Name: The submission name (becomes the filename for generated documents). Omit it when the form has HasNamingConvention=true in search_forms — the server names the submission automatically from its naming convention. Required when HasNamingConvention=false. - mcpRequest.Answers: Array of answer objects, each with Ref (the field ref from get_fields_by_form), Answer (text value for text-based fields) and/or AnswerRef (option ref(s) for selection fields). For file upload fields, a submission must be created as draft and attach_submission_file tool should be used to upload files. If you have no public URL for the file, give the user the ResumeUrl: they upload the file on the draft page in Smarter Drafter, then you call submit_submission. - mcpRequest.IsDraft: Set to true to save as draft (allows later editing), false to submit immediately - Every other field in mcpRequest is optional. Leave it empty unless the user asks for what its description says. Only send what the form asks for: answer only the fields returned by get_fields_by_form, with what the user gave you for this document. When a field's Instructions say not to ask for a value or not to send it, leave that field without an answer. Response: Returns a success/error response with: - SubmissionId: GUID to track this submission - ResumeUrl: Link to edit draft submissions (only present if IsDraft=true) A successful response means document generation has started, not that the user has the files. Important Post-Processing Steps (When IsDraft=false only): 1. Attempt the first download IMMEDIATELY after this call returns. Do NOT wait before the first attempt. 2. If the download returns 404 "Documents were not yet generated", poll every 5 seconds by calling get_submission_generated_documents_url. Do NOT wait 30/45/60 seconds between attempts — the cadence is strictly 5 seconds. Total generation time is typically 5-60 seconds. 3. Download the documents in this STRICT order: DOCX FIRST, then EML (when present), then PDF LAST. Use the returned URLs with proper OTP authentication. CRITICAL: some clients preview whichever file was downloaded LAST — so the PDF MUST be the final download so that it (and only it) is previewed. NEVER download the PDF before the DOCX or EML. 4. Save downloaded files where the user can open them. 5. Present ALL downloaded files to the user so they can save them, using the client's file-presentation capability when one is available. List them in the same order they were downloaded: DOCX FIRST, then EML (when present), then PDF LAST. Do NOT put the PDF first. Give the original files from Smarter Drafter; NEVER make a PDF from the DOCX as a replacement. 6. NEVER display raw generated document URLs to users (they're temporary and require authentication). 7. If you cannot download the files, or you cannot make network requests at all (common reasons: no network access, the download host is blocked or not on your allowed list, or you cannot save files), call get_submission_generated_documents to get them inside the tool resul…
get_fields_by_form
ChatGPTRetrieves all fields for a form, grouped by section. Returns section headings, field labels, field refs (used as answer keys in create_submission), field types, validation rules, and options for select/checkbox/radio fields. Call this after search_forms and before create_submission to understand what answers are required.
get_submission_generated_documents
ChatGPTReturns a submission's generated documents (DOCX, EML, PDF) as files inside this tool result, so no download is needed. Done only when the user has the files: the task is complete only when the user can open or save every file in this result (DOCX, EML when present, PDF). The files in this result are NOT visible to the user yet. Delivered means the user sees each file as a file they can download in your reply, or you saved it with a tool that writes to the user's own computer, where they can open it. A sandbox or workspace that only you can see is not the user's computer. If your client has a separate step to present or output files, you MUST call it. Saving a file somewhere, or adding it to the conversation as context, reference material or an uploaded document, does NOT deliver it. When to Use: - ONLY when you cannot download the files from the URLs returned by get_submission_generated_documents_url, for example because of no network access, the download host is blocked or not on your allowed list, or you cannot save files. If you know you cannot make network requests, call this tool straight away. - In every other case use get_submission_generated_documents_url. Response: - The first content item is JSON with Success, ErrorMessage, SuggestedAction and SubmissionUrl. - When Success=true, each next content item is one embedded file. The file name is the last part of its URI. They come in this order: DOCX first, then EML (when present), then PDF last. Error Handling: - "Submission documents were not yet generated": Re-call this tool every 5 seconds until Success=true. - "Submission doesn't have any generated files": The form makes no documents for these answers. Do NOT call this tool again; tell the user. - "Document generation failed": Do NOT call this tool again; tell the user to retry it from the submissions page in Smarter Drafter. - "The documents are too large to return here": Do NOT call this tool again; give the user the SubmissionUrl. After this call: 1. Turn each file into a file the user can download from your reply. If your client can mark a file as output for the user, use that. Do NOT use options that only make the file readable to you. Keep the order: DOCX FIRST, then EML (when present), then PDF LAST. Give the original files from this result; NEVER make a PDF from the DOCX as a replacement. 2. Before you tell the user the files are ready, check that each one appears in your reply as a file they can download, or you saved it to the user's own computer (not to a sandbox only you can see). A file that only appears as context, or as a source you can search, is NOT delivered. In your final message, name each file you delivered. 3. If you cannot deliver every file as a download, say so plainly, do NOT describe the files as delivered, and give the user the SubmissionUrl as the way to download them. The user signs in there and downloads the documents. 4. Do NOT describe or judge what a file contains (for example, "the document looks empty") unless you opened and read the file itself. Text or token counts from a context import are not reliable. If you did open a file and it is empty or has only placeholder text, tell the user. 5. When a response has a SubmissionUrl, ALWAYS include it in your final message, even when the files were presented, so the user can still get the original documents. NEVER make up this link.
get_submission_generated_documents_url
ChatGPTRetrieves fresh download URLs for a submission's generated documents (DOCX, EML, PDF). Done only when the user has the files: the task is complete only when the user can open or save every generated file (DOCX, EML when present, PDF). Delivered means the user sees each file as a file they can download in your reply, or you saved it with a tool that writes to the user's own computer, where they can open it. A sandbox or workspace that only you can see is not the user's computer. If your client has a separate step to present or output files, you MUST call it. Saving a file somewhere, or adding it to the conversation as context, reference material or an uploaded document, does NOT deliver it. When to Use: - Download URLs from create_submission/submit_submission have expired (OTP valid for 5 minutes only) - Initial download attempt returned 404 "Documents were not yet generated" - Need to re-download documents after initial processing Document Generation Timing: - Documents begin generating when submission is created (IsDraft=false) or when submit_submission is called - Generation typically takes 5-60 seconds - This tool checks submission status before returning URLs Response: - Success=true: Returns fresh URLs with new 5-minute OTP tokens, and SubmissionUrl, a link that opens the submission in Smarter Drafter - Success=false: Returns error if submission not found or documents not yet generated Error Handling: - "Submission documents were not yet generated": Re-call this tool every 5 seconds. Do NOT wait longer than 5 seconds between attempts — the cadence is strictly 5 seconds until Success=true. - "Submission doesn't have any generated files": The form makes no documents for these answers. Do NOT call this tool again; tell the user. - "Document generation failed": Do NOT call this tool again; tell the user to retry it from the submissions page in Smarter Drafter. - "Submission with ID '...' not found": Verify the GUID is correct Usage Flow: 1. Call this tool immediately; if the error is "Submission documents were not yet generated", poll every 5 seconds until Success=true. Stop on any other error. 2. Download the documents in this STRICT order: DOCX FIRST, then EML (when present), then PDF LAST. Use returned URLs with OTP authentication. CRITICAL: some clients preview whichever file was downloaded LAST — so the PDF MUST be the final download so that it (and only it) is previewed. NEVER download the PDF before the DOCX or EML. 3. Save downloaded files where the user can open them 4. Present ALL downloaded files to the user so they can save them, using the client's file-presentation capability when one is available. List them in the same order they were downloaded: DOCX FIRST, then EML (when present), then PDF LAST. Do NOT put the PDF first. Give the original files from Smarter Drafter; NEVER make a PDF from the DOCX as a replacement. 5. NEVER display raw generated document URLs to users (temporary and require authentication) 6. If you cannot download the files (common reasons: no network access, the download host is blocked or not on your allowed list, or you cannot save files), call get_submission_generated_documents to get the files inside the tool result. If that does not work either, give the user the SubmissionUrl. The user signs in there and downloads the documents. Do NOT just tell the user to find them in the dashboard. 7. Before you tell the user the files are ready, check that each one appears in your reply as a file they can download, or you saved it to the user's own computer (not to a sandbox only you can see). A file that only appears as context, or as a source you can search, is NOT delivered. If you cannot deliver every file as a download, say so plainly, do NOT describe the files as delivered, and give the user the SubmissionUrl as the way to download them. In your final message, name each file you delivered. 8. When a response has a SubmissionUrl, ALWAYS include it in your final message, even when the files were presented, so the user can still get the original documents. NEVER make…
search_forms
ChatGPTSearches for available forms by name, description, or long description. Call this first to discover the FormId required by get_fields_by_form and create_submission. Pass an empty string to list all available forms. Max 100 results.
submit_submission
ChatGPTFinalizes a draft submission and initiates document generation. Converts draft to completed submission. Done only when the user has the files: the task is complete only when the user can open or save every generated file (DOCX, EML when present, PDF). Delivered means the user sees each file as a file they can download in your reply, or you saved it with a tool that writes to the user's own computer, where they can open it. A sandbox or workspace that only you can see is not the user's computer. If your client has a separate step to present or output files, you MUST call it. Saving a file somewhere, or adding it to the conversation as context, reference material or an uploaded document, does NOT deliver it. When to Use: - After creating a submission with IsDraft=true in create_submission - After using update_submission_answer or attach_submission_file to add/correct answers in a draft - When ready to generate final documents for a previously saved draft Prerequisites: - Submission must exist with IsDraft=true (created via create_submission) - All required field answers must be provided - Any file uploads should be completed via attach_submission_file What This Does: 1. Validates all required fields have answers 2. Marks submission as submitted (no longer editable) 3. Queues document generation job (DOCX, EML, PDF) 4. Returns download URLs with 5-minute OTP tokens Response: Returns same structure as create_submission: - SubmissionId: The same GUID passed in - ResumeUrl: null (no longer a draft) - Success: true/false - ErrorMessage: Present if validation fails - SuggestedAction: Guidance for fixing validation errors A successful response means document generation has started, not that the user has the files. Post-Submission Steps: 1. Attempt the first download IMMEDIATELY after this call returns. Do NOT wait before the first attempt. 2. If the download returns 404 "Documents were not yet generated", poll every 5 seconds by calling get_submission_generated_documents_url. Do NOT wait 30/45/60 seconds between attempts — the cadence is strictly 5 seconds. Total generation time is typically 5-60 seconds. 3. Download the documents in this STRICT order: DOCX FIRST, then EML(when present), then PDF LAST. Use returned URLs with OTP authentication. CRITICAL: some clients preview whichever file was downloaded LAST — so the PDF MUST be the final download so that it (and only it) is previewed. NEVER download the PDF before the DOCX or EML. 4. Save files where the user can open them 5. Present ALL downloaded files to the user so they can save them, using the client's file-presentation capability when one is available. List them in the same order they were downloaded: DOCX FIRST, then EML(when present), then PDF LAST. Do NOT put the PDF first. Give the original files from Smarter Drafter; NEVER make a PDF from the DOCX as a replacement. 6. If you cannot download the files, or you cannot make network requests at all (common reasons: no network access, the download host is blocked or not on your allowed list, or you cannot save files), call get_submission_generated_documents to get them inside the tool result. Do not wait for a download to fail first. If that does not work either, give the user the SubmissionUrl returned by get_submission_generated_documents_url. 7. Before you tell the user the files are ready, check that each one appears in your reply as a file they can download, or you saved it to the user's own computer (not to a sandbox only you can see). A file that only appears as context, or as a source you can search, is NOT delivered. If you cannot deliver every file as a download, say so plainly, do NOT describe the files as delivered, and give the user the SubmissionUrl as the way to download them. In your final message, name each file you delivered. 8. When a response has a SubmissionUrl, ALWAYS include it in your final message, even when the files were presented, so the user can still get the original documents. NEVER make up this link. Common Errors: - "Required field missing": Call update_submissio…
update_submission_answer
ChatGPTUpdates a single text or option answer in an existing draft submission. This tool takes no files and no URLs: use attach_submission_file for file fields. When to Use: - Correcting answers in draft submissions - Updating fields after initial submission creation Prerequisites: - Submission must exist (use submissionId from create_submission) - For draft submissions: ensure IsDraft=true when created - Field ref must match a field from get_fields_by_form Parameters: - submissionId: The GUID returned by create_submission - fieldRef: The field reference string from get_fields_by_form (e.g., "20001245") - mcpRequest: Contains the new answer value - Answer: String value for text-based fields, at most 8000 characters - AnswerRef: String value for ref of the option when using fields with option e.g. Single or multiple selection Field-Specific Behavior: - Text/Number/etc.: Use Answer property with appropriate format (see create_submission for formats, and the field's Instructions from get_fields_by_form) - A field whose Instructions say not to send a value: do not update it here; the user enters it on the draft page - Multi-select (Checkbox) or single select (radio): Use AnswerRef property with the ref of the option. When multi-select, use option refs joined by ';' - File fields: not supported here; call attach_submission_file with a public URL, or give the user the ResumeUrl from create_submission so they upload the file on the draft page in Smarter Drafter Response: - Success=true: Answer updated successfully - Success=false: Returns ErrorMessage with validation details and SuggestedAction Common Errors: - "Field not found": fieldRef doesn't match any field in the form - "Submission not found": Invalid submissionId - Validation errors: Answer format doesn't match field type requirements After Updating Answers: - For draft submissions: Call submit_submission when all answers are complete - Documents regenerate automatically after submission
create_submission
Claudeget_fields_by_form
Claudeget_submission_generated_documents_url
Claudesearch_forms
Claudesubmit_submission
Claudeupdate_submission_answer
Claude