> ## Documentation Index > Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Tools > Configure workspace tool defaults, per-agent tool access, MCP tools, and custom code tools. Tools let agents take actions and retrieve live data. In V3, tools can come from integrations, MCP connections, custom Python or JavaScript code, built-in Conduit capabilities, and AI-triggered workflows. Open **Build > Agents > Tools** to manage workspace defaults. Open an individual agent and select **Tools** to override access for that agent. ## Workspace Tool Defaults The workspace Tools page has two tabs: | Tab | Use it for | | --------- | ---------------------------------------------------------------------------------------------------------------------- | | **Tools** | Review connected apps that expose tools, create custom tools, and enable custom tools by default across the workspace. | | **Runs** | Inspect recent tool runs and results. | Custom tool workspace defaults are not the final word for every agent. Individual agents can override tool access in their own Tools tab. ## Tool Sources | Source | Where it appears | Notes | | -------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Connection tools** | Workspace Tools and per-agent Tools | Installed through connected apps and integrations, including PMS wrapper tools that let an agent call PMS actions directly. The workspace page lists connections that expose tools; grant or remove access from an individual agent's Tools tab. | | **Custom tools** | Workspace Tools and per-agent Tools | Written in Python or JavaScript inside Conduit. | | **MCP tools** | Per-agent Tools and Operator Tools | Add MCP from the tool settings when the workspace needs external tool servers. | | **Built-in tools** | Per-agent Tools | Conduit-managed tools for native product capabilities, such as scheduling a follow-up, sleeping and waking the agent, and querying the data lake. See [Built-in Tools](#built-in-tools) below. | | **Workflow tools** | Tool pickers and Skills | Active AI-triggered workflows can be exposed as callable tools. | PMS connections can expose two different things, and enabling one does not enable the other: * **Knowledge sync** imports PMS data into Knowledge so agents can retrieve it. See [Knowledge Base](/agent-hub/knowledge-base). * **Connection tools** wrap PMS APIs so an agent can call PMS actions directly during a conversation, instead of only reading synced data. The workspace Tools page currently shows connections that expose tools and custom tools. Built-in tools are configured from the individual agent's Tools tab when available for that agent. ## Per-Agent Overrides Open **Build > Agents**, select an agent, then open **Tools**. Use the agent Tools tab to: * Enable or disable connection tools for that agent * Enable or disable custom tools for that agent * Add MCP access * Review built-in tools available to that agent * Search large tool lists Keep tool access narrow. Agents perform better when they have the tools needed for their job and not every possible action in the workspace. ## Built-in Tools Built-in tools are Conduit-managed capabilities that ship with the product, rather than something a workspace installs or writes. They're reviewed and enabled from an individual agent's Tools tab when available for that agent. | Tool | What it does | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Follow up** | Schedules a future check-in on a conversation instead of requiring the guest to reply right away. The agent can come back to the conversation on its own schedule rather than blocking on an immediate reply. | | **Sleep and wake** | Pauses the agent's own execution and resumes it later, so it can wait on an external event or a time delay without blocking. | | **Data lake query** | Queries the underlying data lake directly, for big-data-style, retroactive analysis across conversations and other workspace data rather than a single live per-conversation lookup. | ## Custom Tools Custom tools extend what agents can do with code. Open **Build > Agents > Tools**, then create a new custom tool. ### Tool Fields | Field | Requirement | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | Lowercase letters, numbers, and hyphens only. No spaces, no leading or trailing hyphen, no consecutive hyphens, and no conflict with internal tool names. | | **Description** | Tell the AI when and why to use the tool. This is model-facing instruction, not just a human label. | | **Language** | Python or JavaScript. | | **Parameters** | Add string, number, boolean, or enum inputs. Mark required fields and describe each parameter clearly. | | **Execution message** | The message shown while the tool runs. | | **Code** | Implement the tool logic in the editor. | ### Test A Custom Tool Use **Test** before saving or publishing tool changes. If the tool has parameters, Conduit asks for test values. The test panel shows JSON output, errors, logs, and runtime so you can verify the behavior before any agent depends on the tool. The editor warns before leaving with unsaved changes. Use Save intentionally after the test output matches the contract you want the agent to rely on. ## Tool Descriptions Tool descriptions are part of the agent instruction surface. Good descriptions answer: * What action does the tool perform? * When should the agent use it? * What information must the agent collect first? * What should the agent do if the tool fails? * What should the agent say after the tool succeeds? ## Operator Tool Access Operator has its own tool settings. Giving an agent access to a tool does not automatically give Operator the same access, and changing Operator's tools does not automatically change a customer-facing agent. Open **Operator > Settings > Tools** when you want Operator to use a tool while helping configure the workspace.