Tools And Apps
Tools and apps expand what an agent can do. Keep the model simple: give each agent the smallest set of capabilities it needs for the job, then add more only when the workflow requires them.
Tool types
| Type | What it is | Typical audience |
|---|---|---|
| Built-in tools | Core platform capabilities such as files, communication, web work, HTTP requests, search, charts, PDFs, and human input. | Users |
| Connected apps | SaaS and app integrations connected through the platform's app connection flows. | Users and admins |
| MCP servers | Model Context Protocol servers that expose external tools or data sources to agents. | Advanced users, admins, developers |
| System skills | Product-level capability bundles such as planning, Meta Agent, connected app channels, or domain-specific skills. | Admins and operators |
| API spec integrations | Selected operations from a published OpenAPI specification, with credentials and per-operation policies. | Organization agent administrators |
| Custom tools | Code-backed tools available where sandbox compute is enabled. | Developers and advanced operators |
Connect only what the agent needs
Before enabling a tool or app, ask:
- Does this agent need the capability for its role?
- Can the tool read or change sensitive data?
- Does it require credentials or OAuth?
- Should use of the tool require approval?
- Is the tool personal, organization-owned, or platform-provided?
Smaller tool sets make behavior easier to understand and debug.
App connections
Connected apps let an agent use supported external services. Some app flows are interactive: you choose an app, connect it, then assign it to the agent.
See Connect Apps.
MCP servers
MCP servers are a flexible way to expose tools and data. They can be personal, Organization-private, Team-scoped, Organization-scoped, or platform-managed depending on deployment and admin policy. Ordinary assignments and inherited managed connections have different access controls.
See MCP Servers and Organization MCP Servers.
API spec integrations
Organization agent administrators can import a bundled OpenAPI 3 specification, publish selected operations, and bind credentials and approvers to an agent. See Build Integrations From API Specs for supported payloads, revisions, approvals, and connection changes.
System skills and profiles
System skills are higher-level product capabilities. Examples include runtime planning, Meta Agent, connected app channels, or other managed skill bundles.
Admins may configure profiles for system skills in some deployments. Treat these as workspace-level capability settings, not ordinary chat prompts.
See System Skills And Profiles.
Credentials
Do not paste credentials into chat. If a tool or app needs a password, API key, token, or environment-style value, use the platform's secrets flow.
Troubleshooting
If an agent cannot use a tool:
- Confirm the tool or app is enabled for that agent.
- Confirm OAuth or credential setup is complete.
- Check whether the tool is available in the current personal or organization context.
- Review the timeline for a pending approval or secret request.
- Ask the agent to explain which tool it tried to use and what blocked it.