Datasite

Invite a user to a Datasite project by email address and assign them a role. Use only for an email address that is not yet a member of the project. This tool does not change or reassign the role of an existing member, and it does not modify any existing membership. Calling it for someone who is already a member will send them another invitation email. Specify the role by name (e.g., "Reviewer") or by roleId; roleName is resolved automatically.

inviteUser

List the contents of filerooms and folders in a Datasite project. Returns item metadata — names, IDs, types (FILEROOM, FOLDER, DOCUMENT, PLACEHOLDER, SANDBOX), statuses, file types, and publishing states — but NOT document text. Use this to navigate the folder tree, see what documents exist and their metadata, or find where content is located before creating, uploading, or modifying it. To find information inside documents (e.g. clauses, risks, or specific content), use searchDocuments instead. Behavior by parameters: - No metadataId: Returns the top-level fileroom listing with IDs. - With metadataId: Returns contents under that folder or fileroom. depth controls how much of that folder to list. - depth (default 1, max 5): Controls how many levels deep to traverse. depth=1 returns immediate children only. depth > 1 follows folder contents breadth-first, returning all items with depth and path columns so you can understand the visible structure in one call instead of browsing level by level. Must be between 1 and 5. - foldersOnly (default true): When true, only folder-type items (FILEROOM, FOLDER, SANDBOX, INBOX) are returned. Set to false to include documents in the results. Applies at all depth levels. - limit: Maximum matching direct children to fetch for each folder that is read. Defaults to 1,000. Must be between 1 and 1,000. - skip: Number of matching direct children to skip before returning results. Defaults to 0. Must be 0 or greater. Only valid with depth=1. Use a returned node's listingStatus.nextCall to continue reading that specific folder. Nodes omit listingStatus when there is nothing else to do. A returned listingStatus means the node's folder listing is incomplete or needs attention. NOT_READ means contents were not read, usually because depth stopped there or a fetch failed. PARTIAL means more direct children are available and listingStatus.nextCall gives the next listFolderContents call. The listing may include items with type SANDBOX (named "Staging Folder"). A sandbox is a staging area where content is uploaded before being published to regular filerooms. PREPARE projects use the sandbox exclusively for uploads — all content must go through the Staging Folder.

listFolderContents

List all Datasite projects you have access to, optionally enriched with subscription context. Use this to find projects by name, ID, state, or to discover which subscription a project belongs to. Set includeSubscriptionInfo=true to include subscription details.

listProjects

List all Datasite subscriptions you have access to. Returns subscription name, ID, and allowed offering types. Use this to find which subscription to use when creating a new project.

listSubscriptions

Create Q&A question drafts, update questions, or categorize Q&A questions in a Datasite project. This is the default tool for creating question drafts when the current user is not on an ANSWER team. Use submitQuestionOnBehalf only after getMyQandaTeam confirms the current user is on an active ANSWER team. action=CREATE: creates an IN_PROGRESS draft only for the caller's QUESTION team; requires categoryId, gateId, and workflowIndex. RULES FOR CREATE: - Call getQandaGateContext first to confirm what gates the user is a part of, and therefore, what categories they can submit questions for. - assignedToIds may contain only users from gateMemberUserIds returned by getQandaGateContext. Omit it to assign every gate member. - If the user requests to assign no other users to the question, pass an empty array into the assignedToIds parameter. Else, omitting it will assign every gate member. - Use getMyQandaTeam to identify the current user's Q&A team, and getQAStatus with includeCategories=true to list visible categories. If a requested category is not returned, tell the user it may either not exist or may not be accessible to them; do not state that it definitely does not exist. The question is not submitted. - Ideally, before creation, notify the user of the fact that questions will be created as draft. - Once a question is created as a draft, provide the user with a URL to go to the UI to view the draft. - If the user mentions that they want to attach documents to the question, the listFolderContents should be called to list the available documents BEFORE creating the question. DocumentIds need to be passed into the tool to properly attach the documents. - DO NOT ATTEMPT TO CREATE A QUESTION DRAFT IF THE USER IS NOT IN THE GATE. action=UPDATE: requires questionId and closed. Supports closing/reopening via the closed param. action=CREATE_CATEGORY: requires categoryName.

manageQuestion

Create or update a role in a Datasite project. action=CREATE: requires name. action=UPDATE: requires roleId, optional name to rename.

manageRole

Move files or folders to a different location within a Datasite project. This is a destructive operation. User confirmation is recommended before execution. When moving a folder, all children are moved automatically. Moved items keep their current permissions and publishing status. Each result includes a url to review the moved item at its new location. Supports moving up to 100 total items (including all children) for synchronous moves. If bulk move is enabled, moves exceeding 100 items are processed asynchronously and return an operation ID.

moveContent

Search across document content in a Datasite project using AI-powered semantic search. Applies to Diligence and Acquire projects. Returns matching text passages from inside documents with relevance scores, page numbers, and source paths. Each result includes a url (when the source document is identifiable) that opens the source document and highlights the matched passage — when citing information from a result, always use that result's url as the citation link, never a project-level or homepage URL from other tools. Use this whenever you need to find information, clauses, risks, or answers within documents — not for navigating folder structure. Blueflame search is only available for eligible users on Diligence and Acquire projects. If the project type is unsupported or the user does not have access, this tool returns structured, actionable guidance instead of results. Not all users can self-activate Blueflame; the guidance reflects the appropriate next step for the user's role and project. Limit caps at 25. Set rerank=true to rerank results by relevance at the cost of higher latency.

searchDocuments

When to use: Customer-facing help centre articles explaining how Datasite features work — e.g. "how do I create a tracker," "what is a fileroom," "why can't I invite this user," "what does this setting do." Does NOT search content inside a customer's project or data room — use searchDocuments for that. What this tool returns: A list of scored passages, ordered by relevance (highest first). Each result includes: score, matching_text (the actual passage content — use this for your answer), source_url, article_id, title, and section. article_id, title and section are sometimes blank or missing (older indexed passages) — still cite the source_url when this happens. Lower-scoring results may be less relevant; don't treat all returned results as equally authoritative. Response requirements: Attach source_url close to the claim it supports, rather than batching all citations at the end of the response. Name the article title and section alongside each citation when available. Never restate help content without a citation. If no results are returned, tell the user no help article matched. Do not fall back on your own knowledge of Datasite. If results are returned but none are actually relevant to the query (check scores and content, not just presence of results), tell the user no relevant help article was found — do not stretch a low-relevance passage to fit the question. Before sending your response, confirm every claim has a source_url attached, or revise.

searchHelpDocs

Create a new Datasite project and optionally set up its initial content structure in one call. IMPORTANT — CONFIRM REQUIRED FIELDS BEFORE CALLING: - datacenter is always an explicit user choice. If the user has not stated a region, STOP and ask before calling this tool. Do not infer datacenter from the user's apparent location, the project name, the conversation topic, or prior projects. This is a data-residency decision with compliance implications — never default to USA (or any other region) just because it is listed first or seems likely. - useCase, industryType, and transactionValue should come from the user's description of the deal. If the user has given enough freeform context to map confidently to the enum values, you may do so. If not, ask a short clarifying question first. Do not fabricate values that are unsupported by what the user has actually said. One round-trip to confirm is always cheaper than creating a project with wrong metadata. SUBSCRIPTION: subscriptionId is optional only in limited cases. Omitting it works when the user has no enterprise subscriptions — the service will resolve their default usage subscription automatically. If the user may belong to an enterprise account or have access to multiple subscriptions, call listSubscriptions first and ask them which to use, then pass its ID as subscriptionId. If a create call without subscriptionId fails because a subscription is required, fall back to listSubscriptions and ask the user to pick one. A Staging Folder (sandbox) is automatically created for the project. If contentPaths is provided, paths default to folders inside the sandbox unless an explicit type override is provided. contentPaths is a flat JSON array where each entry is a full path string plus optional type and published flag: - path (required): Full slash-separated path, e.g. "/Financial/Q1" or "/Legal" - type (optional): Override type for the final segment of this path — FILEROOM or FOLDER (auto-inferred if omitted) - published (optional): Whether the final segment of this path is visible to non-admin users (defaults to false). Not applicable in PREPARE projects — publishing is not supported. Shared ancestor segments are deduplicated automatically. To set type on an ancestor, list it as its own entry alongside its children (e.g. {"path":"/Financial","type":"FILEROOM"} and {"path":"/Financial/Q1"}). Example: [{"path":"/Financial/Q1"},{"path":"/Financial/Q2"},{"path":"/Legal"}] Do not prefix fileroom or folder names with numbers or numeric sequences (e.g. "01.", "1.", "1 -"). Use plain descriptive names only. Do not suggest publishing content for PREPARE projects — publishing is not a supported feature in PREPARE.

setupProject

Submit one or more Q&A questions on behalf of a question team from an answer-team admin context. - BEFORE using this tool, call getMyQandaTeam for the project. Use submitQuestionOnBehalf only when getMyQandaTeam returns onQandaTeam=true, teamType=ANSWER, active=true, and allowedToSubmit=true. - If getMyQandaTeam shows the current user is not on an active ANSWER team, do not use submitQuestionOnBehalf. - If getMyQandaTeam shows the current user is in the QUESTION team, use manageQuestion for question-team draft creation instead. - If the user mentions that they want to attach documents to the questions, the listFolderContents should be called to list the available documents BEFORE creating the questions. Each question has it's own documentIds collection that is there to express what documents the user wants to link to each question. - Use getMyQandaTeam to confirm the current user's team context, and getQAStatus with includeCategories=true to find visible category names and ids. If a requested category is not returned, tell the user it may either not exist or may not be accessible to them; do not state that it definitely does not exist. - Use getQAStatus to get data about the question teams currently configured in the Q&A enabled project. - Use getQandaGateContext to find the correct gate/workflow information for the respective category in the question team. - Questions must be supplied through the questions array, even when importing a single question. - Imported questions are created as in-progress question-team drafts assigned to the first gate members. - User must be notified that the question will be created as a draft and will be assigned to all team members in the corresponding question team workflow, based on category. - It is possible you will be extracting text from an Excel file. If so, make sure the question content is left totally unchanged -- do not modify it in any way unless requested to do so. - Do not provide the user with any URLs to look at the questions in the platform/UI once they have been posted. Since they're submitted as drafts, they become visible to question team members only. - After the questions are created, let the user know they're saved as drafts and won't be visible to any answer team member—including the user—until the question team submits them

submitQuestionOnBehalf

Update a document or folder in a Datasite project. Supports renaming, and supports changing publishing status only for non-PREPARE projects. Identify the item by metadataId or human-readable path (e.g., "Financial/Q1 Reports"). Do not suggest publishing status changes for PREPARE projects — publishing is not a supported feature in PREPARE.

updateContent

Activate or deactivate a user's membership in a Datasite project. Use getMembers to find user IDs. Status must be ACTIVATED or DEACTIVATED.

updateMembership

Get a link to manage content permissions for a Datasite project via the web application. Optionally provide a fileroom or folder ID to navigate directly to its permissions page. Returns a browser URL where the user can review and update permissions manually.

updatePermissions

Get a link to upload documents to a Datasite project via the web application. Specify the destination as a human-readable path (e.g., "Financial/Q1 Reports") or a direct folder ID. Returns a browser URL that opens the target folder in the Datasite web application, where the user can complete the upload. For PREPARE projects, uploads must target the Staging Folder (sandbox). Browse content first to find the sandbox, then use its path or ID as the destination.

uploadContent