Skip to main content
Glama

agent_activate

Activate specialized AI agents for IT support, security testing, sales assistance, or team collaboration tasks within the MCP Instruct server.

Instructions

Activate a specialized AI agent (IT Expert, Hacker, Sales, Blue/Red/Purple Team)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentYesAgent ID to activate

Implementation Reference

  • Executes the agent_activate tool: initializes AgentManager, sets the specified agent as active if valid, retrieves agent details and tools, returns success message with available default tools.
    case 'agent_activate': {
      await am.initialize();
      const { agent } = args as any;
      const success = am.setActiveAgent(agent);
      
      if (!success) {
        throw new Error(`Agent not found: ${agent}`);
      }
      
      const activeAgent = am.getActiveAgent();
      const tools = getAgentTools(agent);
      
      return {
        content: [
          {
            type: 'text',
            text: `✅ Activated ${activeAgent?.name}\n\nTools available: ${tools?.defaultTools.join(', ') || 'none'}`
          }
        ]
      };
    }
  • src/index.ts:348-362 (registration)
    Registers the agent_activate tool in the tools array returned by ListToolsRequestHandler, including name, description, and input schema with required 'agent' parameter from predefined enum.
    {
      name: 'agent_activate',
      description: 'Activate a specialized AI agent (IT Expert, Hacker, Sales, Blue/Red/Purple Team)',
      inputSchema: {
        type: 'object',
        properties: {
          agent: {
            type: 'string',
            enum: ['it-expert', 'ethical-hacker', 'sales-expert', 'blue-team', 'red-team', 'purple-team'],
            description: 'Agent ID to activate'
          }
        },
        required: ['agent']
      }
    },
  • AgentManager.setActiveAgent: Core logic to activate an agent by setting this.activeAgent to the provided ID if the template exists in loaded agents, returns success boolean.
    setActiveAgent(id: string): boolean {
      if (this.templates.has(id)) {
        this.activeAgent = id;
        return true;
      }
      return false;
    }
  • getAgentTools: Retrieves the predefined AgentToolset (tools list and defaultTools) for the given agent ID from AGENT_TOOLSETS lookup.
    export function getAgentTools(agentId: string): AgentToolset | undefined {
      return AGENT_TOOLSETS[agentId];
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Activate') but doesn't explain what activation entails—e.g., whether it changes system state, requires permissions, has side effects (like deactivating other agents), or what happens post-activation (e.g., agent availability or response format). This leaves critical behavioral traits unspecified for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action ('Activate') and lists agent types without unnecessary details. Every word contributes to understanding the tool's scope, making it appropriately sized and well-structured for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a mutation operation with no annotations or output schema), the description is incomplete. It lacks information on behavioral outcomes (e.g., what activation means, success indicators, or error conditions) and doesn't address usage context relative to siblings. For a tool that likely changes system state, more detail is needed to guide an AI agent effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'agent' parameter fully documented via enum values. The description adds no additional parameter semantics beyond what the schema provides—it lists agent types that match the enum but doesn't explain their roles or differences. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't detract either.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Activate') and the resource ('specialized AI agent'), listing specific agent types (IT Expert, Hacker, Sales, Blue/Red/Purple Team). It distinguishes the tool's purpose from siblings like agent_list (list agents) or agent_get_active (get active agent), though it doesn't explicitly contrast them in the description text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether agents must be available or configured), when not to use it, or direct comparisons to siblings like agent_switch_quick (which might offer a quicker activation method). Usage is implied by the action 'activate,' but no explicit context is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hlsitechio/mcp-instruct'

If you have feedback or need assistance with the MCP directory API, please join our Discord server