Skip to main content
Under the hood, invoking an agent works like calling a function: the target agent runs independently with its own instructions and tools, then its output is returned to the calling agent. You can target either an agent from your current project or a system-wide core agent.
This tool has Default status, meaning it’s production-ready and available on all subscription plans.

Overview

The Agent Tool creates a powerful multi-agent architecture where agents can:

Agent Orchestration

Coordinate multiple specialized agents for complex tasks

Task Delegation

Delegate specific subtasks to expert agents

Knowledge Sharing

Share context and information between agents

Workflow Automation

Build sophisticated multi-step agent workflows

Configuration Parameters

select
required
The agent to invoke when this tool is used
Options:
  • Project agents - Agents created in your current project
  • Core agents - System-wide specialized agents
    Note: The target agent must be active and configured properly

Setup Instructions

1

Create Target Agent

First, ensure you have created and configured the agent you want to invoke
2

Navigate to Tools

Go to the Tools section in your project dashboard
3

Create Agent Tool

Click Create Tool and select Agent Tool
4

Configure Tool Details

Provide a descriptive name and description for the tool
5

Select Target Agent

Choose the agent you want to invoke from the dropdown list
6

Test Agent Tool

Use the test button to verify the agent invocation works correctly
7

Add to Parent Agent

Assign this tool to the orchestrator or parent agent that will use it

Agent Types

Project Agents

Custom agents created within your project:
  • Custom Configuration: Tailored to your specific needs
  • Project-Scoped: Available only within the current project
  • Full Control: Complete control over prompts and settings
  • Flexible: Can be modified and optimized as needed

Core Agents

System-wide specialized agents available across projects:
  • Pre-Configured: Ready to use with optimal settings
  • System-Wide: Available across all projects
  • Maintained: Regularly updated and improved
  • Specialized: Designed for specific common tasks

Configuration Examples

Customer Support Escalation

Use Case: A general support agent can escalate technical questions to a specialized technical support agent with deep product knowledge.

Multi-Language Support

Use Case: An English-speaking agent can invoke a translation agent to provide responses in Spanish.

Data Analysis Pipeline

Use Case: A general business intelligence agent can delegate financial analysis to a specialized financial analyst agent.

Content Generation Workflow

Use Case: A content creation agent can invoke an SEO specialist to optimize generated content.

Multi-Agent Architectures

Hierarchical Architecture

  • Orchestrator Agent delegates to:
    • Research Agent — uses the Web Search Tool and the Database Tool
    • Analysis Agent — uses the Data Processing Tool and the Analytics Tool
    • Writing Agent — uses Content Templates and Style Guidelines
Pattern: Single orchestrator delegates to specialized agents Benefits: Clear responsibility, easy to maintain Use Cases: Customer service workflows, content creation pipelines

Collaborative Architecture

  1. Agent 1: Intake
  2. Agent 2: Processing
  3. Agent 3: Quality Check
  4. Agent 4: Delivery
There are two feedback loops on top of this sequence: Quality Check can send work back to Processing (feedback), and Delivery can send work back to Quality Check (review). Pattern: Agents pass work sequentially with feedback loops Benefits: Quality control, iterative improvement Use Cases: Document processing, data validation workflows

Specialist Pool Architecture

  • Router Agent routes to:
    • Technical Agent — handles Issue Resolution
    • Sales Agent — handles Opportunity Mgmt
    • Billing Agent — handles Payment Processing
    • General Agent — handles General Inquiries
Pattern: Router agent directs to appropriate specialist Benefits: Efficient routing, specialized expertise Use Cases: Customer support, ticketing systems

Use Cases & Applications

Customer Support Tiers

Content Creation Pipeline

Sales Qualification Workflow

Data Processing Pipeline

Context Passing & Data Flow

Input Context

When an agent invokes another agent through the Agent Tool:

Response Format

The invoked agent returns:

Best Practices

Agent Design

Single Responsibility: Design each agent with a specific, well-defined purpose for better reliability and maintainability.
  • Clear Objectives: Define precise goals for each agent
  • Focused Expertise: Limit each agent’s scope to specific tasks
  • Consistent Interfaces: Standardize how agents communicate
  • Error Handling: Implement robust error handling and fallbacks
  • Testing: Thoroughly test agent interactions

Context Management

Performance Optimization

Issue: Multiple agent invocations increase latency Solution: Design direct paths to specialist agents Example: Instead of A→B→C, allow A to directly invoke C when appropriate
Issue: Sequential agent calls are slow Solution: Invoke independent agents in parallel Example: Run data validation and enrichment agents simultaneously
Issue: Redundant agent invocations waste resources Solution: Cache agent responses for common queries Example: Cache translation results, frequently used analyses
Issue: Poor routing leads to multiple handoffs Solution: Implement smart routing based on query analysis Example: Analyze query intent before selecting specialist agent

Security Considerations

Access Control: Ensure agents only invoke other agents they have permission to access. Prevent unauthorized agent chains.
  • Permission Boundaries: Define clear permission boundaries
  • Audit Logging: Log all agent invocations for security audits
  • Data Privacy: Ensure sensitive data is handled appropriately
  • Rate Limiting: Prevent agent invocation abuse IN PROGRESS
  • Monitoring: Monitor for unusual agent invocation patterns

Monitoring & Analytics

Key Metrics

Track important multi-agent performance indicators:

Workflow Visualization

Monitor agent interaction patterns:
  1. User Query arrives at the Router Agent
  2. Router Agent distributes queries to:
    • General Agent — 40% of queries
    • Technical Agent — 35% of queries
      • Escalates 20% of its queries to Engineering Escalation
    • Billing Agent — 15% of queries
      • Escalates 5% of its queries to Manager Approval
    • Sales Agent — 10% of queries

Troubleshooting

Common Issues

Symptoms: Target agent cannot be invoked Solutions:
  • Verify target agent ID is correct
  • Ensure target agent is active
  • Check agent permissions
  • Confirm agent exists in project or core agents
Symptoms: Invoked agent lacks necessary context Solutions:
  • Verify context is being passed correctly
  • Check context size limits
  • Ensure conversation history is maintained
  • Review agent input configuration
Symptoms: Agents invoking each other in loops Solutions:
  • Implement invocation depth limits
  • Add circular reference detection
  • Review agent tool configuration
  • Redesign agent workflow to prevent loops
Symptoms: Slow multi-agent workflows Solutions:
  • Optimize agent invocation paths
  • Implement parallel processing
  • Cache frequent agent responses
  • Reduce unnecessary agent hops

Advanced Patterns

Consensus Building

Multiple agents collaborate to reach consensus:

Dynamic Agent Selection

Smart routing based on query analysis:

Agent Specialization Layers

Progressively specialized agents:

Next Steps

Create Your First Agent Tool

Set up agent-to-agent communication

Multi-Agent Patterns

Learn advanced multi-agent architectures

Other Tools

Explore other available tools

API Reference

View the tools API documentation