add_document
ChatGPTFinalize one prepared add operation, which saves the new file into an existing folder of the matter. Use after the file has been uploaded for a request_document_upload operation with intent add. It never creates a folder (create_folder does that, under its own capability) and never overwrites an existing file: a file with the same name in the folder returns conflict and saves nothing. The result is final and carries the destination, a status of saved, conflict, or not_saved, and a plain-language message for the user. No follow-up check is needed, and a write is never resent.
create_folder
ChatGPTCreate one new folder inside an existing folder of a matter. Use when the user wants documents organized into a folder that does not exist yet. Requires the Create Folders capability. The parent is one exact folder_id and folder_path pair from list_granted_folders for the same matter_id, used unchanged in parent_folder_id and parent_folder_path (the matter root is "/"); a folder_path list_granted_folders did not return is rejected. name is one folder name without "/" or "\". idempotency_key is a stable key for this creation. When verified, the response returns the new folder's exact folder_id and folder_path, usable as a move_document destination. conflict means a folder with that name already exists in the parent, and that folder is the target. The matter is identified by matter_id or by matter_name, the exact display name from list_granted_matters. The response reports the matter, destination, and exact status. verified means the change is confirmed in the live folder tree; conflict means nothing changed; accepted, in_progress, acceptance_unknown, verification_mismatch, and verification_timed_out mean the change is not yet confirmed. Repeating the identical call with the same idempotency_key re-reads the folder tree and never dispatches a second write; a new idempotency_key is a new request.
list_granted_documents
ChatGPTList the documents in one accessible matter. Use to browse a matter or to find a document_id. Each call inspects at most 20 candidates, so limit is a maximum, not a page size; paging continues through next_cursor with the same limit until next_cursor is absent, including after an empty page. An invalid_cursor error means the results changed, and paging restarts without a cursor. The matter is identified by matter_id or by matter_name, the exact display name from list_granted_matters.
list_granted_folders
ChatGPTList the exact folder_id and folder_path pairs in one matter that can receive an added document, a moved document, or a new folder. Use before request_document_upload, create_folder, or move_document. The matter root is returned last as folder_path "/". Each pair is used exactly as returned. When several pairs are returned and the user has not named a folder, the folder choice is the user's. An empty result means no valid add target is currently available. The matter is identified by matter_id or by matter_name, the exact display name from list_granted_matters.
list_granted_matters
ChatGPTList the matters this LawY connection can access. Use first to find the matter_id other tools take, or when the user asks which matters are available.
move_document
ChatGPTMove one existing document into a different existing folder of the same matter. Use when the user asks to organize or file a document. Requires the Move Documents capability. Only the folder changes; content, versions, and name stay, and moving the document back restores its previous place. document_id comes from list_granted_documents or search_granted_documents. The destination is one exact folder_id and folder_path pair from list_granted_folders for the same matter_id, used unchanged; a folder_path list_granted_folders did not return is rejected. idempotency_key is a stable key for one intended move. A document already in the destination returns verified with no change. conflict means the destination already holds a document with that name. The matter is identified by matter_id or by matter_name, the exact display name from list_granted_matters. The document is identified by document_id or by document_name, the exact display name from list_granted_documents; a name that matches no authorized document, or more than one, returns invalid_input with the authorized close matches. The response reports the matter, destination, and exact status. verified means the change is confirmed in the live folder tree; conflict means nothing changed; accepted, in_progress, acceptance_unknown, verification_mismatch, and verification_timed_out mean the change is not yet confirmed. Repeating the identical call with the same idempotency_key re-reads the folder tree and never dispatches a second write; a new idempotency_key is a new request.
read_document_text
ChatGPTRead the current text of a document, one page per call: a page holds at most max_characters characters (default 50,000, maximum 60,000) starting at offset, and a page that ends before the end of the text reports truncated true with the next_offset that starts the following page. Use for reading, analysis, extraction, comparison, summarization, and derivative work; text is the default read for all read-only work. When the text is empty or not enough, for example an image, scan, or diagram, read_original_document returns the original file instead. The response carries one opaque source_reference for the document, text revision, and read time: provenance, not authorization, valid only unchanged in the source_references of a request_document_upload call for an artifact this document supported. The matter is identified by matter_id or by matter_name, the exact display name from list_granted_matters. The document is identified by document_id or by document_name, the exact display name from list_granted_documents; a name that matches no authorized document, or more than one, returns invalid_input with the authorized close matches.
read_original_document
ChatGPTRead the original file of a document as a LawY download URL, with the current version and SHA-256 baseline an update needs. Use for read-only work when a listed document has document_text_available false or its text is not enough (images, scanned PDFs, diagrams, dashboards, layout, tables) and the connection allows reading original documents, or before preparing an update of the document. Text stays the default read when it is usable. The URL is fetched with a GET and expires five minutes after the call. A read is not needed before adding a new document. The response also carries one opaque source_reference for the document, version, and read time: provenance, not authorization or a baseline, valid only unchanged in the source_references of a request_document_upload call for an artifact this document supported. The matter is identified by matter_id or by matter_name, the exact display name from list_granted_matters. The document is identified by document_id or by document_name, the exact display name from list_granted_documents; a name that matches no authorized document, or more than one, returns invalid_input with the authorized close matches.
request_document_upload
ChatGPTPrepare one upload: a new file in a matter folder (intent add) or replacement content for an existing document (intent update). Use to save an artifact into a matter or to update a document; finalization goes through add_document or update_existing_document with only operation_id. Any file type is allowed, for example .docx or .pdf; no media_type or filename-extension list is enforced, and the file is stored as received. Both intents take idempotency_key, filename, media_type, exact_byte_count, the lowercase sha256 of the exact bytes, and source_references from the reads that supported the artifact. An add target is one exact folder_id and folder_path pair from list_granted_folders for the matter, used unchanged; matter_id is not a folder_id, and a folder_path list_granted_folders did not return is rejected. When list_granted_folders returns more than one pair and the user has not named a folder, the folder choice is the user's; when it returns no pair, no valid add target is currently available. An update target is the existing document with current_version and baseline_sha256 unchanged from its read_original_document response. The response carries the upload URL and exact signed headers, and repeats the matter, folder, filename, format, and create-or-update mode. A failed write is not retried.
search_granted_documents
ChatGPTSearch the documents this LawY connection can access, across all accessible matters or within one. Use when the user describes a document by content or topic rather than by name. Relevance is comparable only within one matter.
update_existing_document
ChatGPTFinalize one prepared update operation, which replaces the content of an existing document. Use after the replacement file has been uploaded for a request_document_upload operation with intent update. The update is based on a read_original_document baseline; if the document changed since that read, it stops with stale_original and nothing is replaced, and a new update is prepared from a fresh read. The result is final and carries the destination, a status of saved, conflict, or not_saved, and a plain-language message for the user. No follow-up check is needed, and a write is never resent.
add_document
Claudeappend_document_upload_chunk
Claudecomplete_document_upload_chunks
Claudeconfirm_document_upload_egress_failure
Claudecreate_folder
Claudelist_granted_documents
Claudelist_granted_folders
Claudelist_granted_matters
Claudemove_document
Clauderead_document_text
Clauderead_original_document
Clauderequest_document_upload
Claudesearch_granted_documents
Claudestart_document_upload_chunks
Claudeupdate_existing_document
Claude
