Skip to main content

Tools

Custom Tools extend your agent beyond built-in capabilities by connecting to external MCP (Model Context Protocol) servers — hosted anywhere, doing anything.

How to get there: Sidebar → Tools (Admin only)


What is a Custom Tool?

A small, self-contained integration that your agent's Subagents can invoke:

  • Call external APIs
  • Parse or transform data
  • Interact with third-party services (CRMs, databases, notification systems)
  • Any action your MCP server exposes

Creating a Custom Tool

  1. Navigate to Tools in the sidebar.
  2. Click "Create tool".
  3. Fill out the form:
FieldRequiredDescription
Tool nameYesDescriptive name (helps AI decide when to use it)
DescriptionWhat the tool does and when to use it
Server URLYesPublic HTTPS endpoint of your MCP service
API KeyAuthentication key (if your server requires one)
  1. Click Create.
  2. The tool appears in your list with Edit and Delete actions.

Create custom tool dialog


Attaching a Custom Tool to a Subagent

Via Manual Mode

  1. Composer → select Subagent → Configuration → Tools section
  2. Click Add tool
  3. Select your Custom Tool from the list
  4. Save & Deploy

Add tool catalog

Via Assisted Mode (Composer)

Just tell the Composer:

"Add my [tool name] to this subagent"

The system handles the attachment automatically on the selected Subagent.


Managing Custom Tools

ActionHow
EditOpen the tool card → update fields → Save
DeleteSelect Delete → confirm deletion
View statusTool cards show connection status

Custom tool card list


Best Practices

PracticeWhy
Use HTTPSSecure communication between xMagic and your server
Rotate API keysMinimize exposure if a key is compromised
Return structured JSONHelps the agent parse and use responses effectively
Include request IDs in logsEasier debugging when things go wrong
Handle timeouts gracefullyReturn meaningful errors rather than hanging
Write clear descriptionsThe AI uses the description to decide when to invoke the tool

MCP Server Requirements

Your MCP server should:

  • Be publicly accessible via HTTPS
  • Respond within a reasonable timeout (< 30 seconds recommended)
  • Return JSON responses
  • Handle authentication via API key header (if configured)
  • Expose tool capabilities that the xMagic platform can discover