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:
TabUse it for
ToolsReview connected apps that expose tools, create custom tools, and enable custom tools by default across the workspace.
RunsInspect 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

SourceWhere it appearsNotes
Connection toolsWorkspace Tools and per-agent ToolsInstalled through connected apps and integrations. The workspace page lists connections that expose tools; grant or remove access from an individual agent’s Tools tab.
Custom toolsWorkspace Tools and per-agent ToolsWritten in Python or JavaScript inside Conduit.
MCP toolsPer-agent Tools and Operator ToolsAdd MCP from the tool settings when the workspace needs external tool servers.
Built-in toolsPer-agent ToolsConduit-managed tools for native product capabilities.
Workflow toolsTool pickers and SkillsActive AI-triggered workflows can be exposed as callable tools.
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.

​
Custom Tools

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

​
Tool Fields

FieldRequirement
NameLowercase letters, numbers, and hyphens only. No spaces, no leading or trailing hyphen, no consecutive hyphens, and no conflict with internal tool names.
DescriptionTell the AI when and why to use the tool. This is model-facing instruction, not just a human label.
LanguagePython or JavaScript.
ParametersAdd string, number, boolean, or enum inputs. Mark required fields and describe each parameter clearly.
Execution messageThe message shown while the tool runs.
CodeImplement 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.