Skip to main content
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: 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

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.
  • 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.

​
Custom Tools

Custom tools extend what agents can do with code. Open Build > Agents > Tools, then create a new custom tool.

​
Tool Fields

​
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.