Skip to main content
Glama

agent_switch_quick

Switch between predefined agent roles like IT, hacker, sales, or color-coded teams to adapt AI behavior for specific tasks.

Instructions

Quick switch agent using shorthand (it/hacker/sales/blue/red/purple)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesQuick switch type

Implementation Reference

  • src/index.ts:363-377 (registration)
    Registers the 'agent_switch_quick' tool including its input schema for quick agent switching using shorthand names.
    {
      name: 'agent_switch_quick',
      description: 'Quick switch agent using shorthand (it/hacker/sales/blue/red/purple)',
      inputSchema: {
        type: 'object',
        properties: {
          type: {
            type: 'string',
            enum: ['it', 'hacker', 'sales', 'blue', 'red', 'purple'],
            description: 'Quick switch type'
          }
        },
        required: ['type']
      }
    },
  • Tool handler that initializes AgentManager, performs quick switch via am.quickSwitch(type), validates success, and returns confirmation with active agent name.
    case 'agent_switch_quick': {
      await am.initialize();
      const { type } = args as any;
      const success = am.quickSwitch(type);
      
      if (!success) {
        throw new Error(`Invalid agent type: ${type}`);
      }
      
      const activeAgent = am.getActiveAgent();
      return {
        content: [
          {
            type: 'text',
            text: `✅ Switched to ${activeAgent?.name}`
          }
        ]
      };
    }
  • Core logic of agent_switch_quick: maps shorthand types to full agent IDs and delegates to setActiveAgent, returning success boolean.
    quickSwitch(type: 'it' | 'hacker' | 'sales' | 'blue' | 'red' | 'purple'): boolean {
      const mapping: Record<string, string> = {
        'it': 'it-expert',
        'hacker': 'ethical-hacker',
        'sales': 'sales-expert',
        'blue': 'blue-team',
        'red': 'red-team',
        'purple': 'purple-team'
      };
    
      const id = mapping[type];
      if (id) {
        return this.setActiveAgent(id);
      }
      return false;
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 'Quick switch agent', implying a mutation operation that changes the active agent, but doesn't specify whether this requires permissions, what happens to the previous agent, if the switch is reversible, or any side effects like rate limits. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise and front-loaded, consisting of a single, efficient sentence that conveys the core action and key details (shorthand options). Every word earns its place, with no redundant or unnecessary information, making it easy to parse quickly.

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 this is a mutation tool (implied by 'switch') with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, side effects), doesn't explain the return values or what 'quick switch' entails operationally, and offers minimal guidance on usage relative to siblings. For a tool that changes system state, this is inadequate.

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 'type' parameter fully documented via an enum and description. The description adds value by listing the enum values ('it/hacker/sales/blue/red/purple') and implying they are shorthand options, but doesn't provide additional context like what each type represents or how they differ. Given the high schema coverage, a baseline score of 3 is appropriate.

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 ('Quick switch agent') and the resource ('agent'), making the purpose understandable. It specifies the method ('using shorthand') and lists the available shorthand options, which helps distinguish it from other agent-related tools like 'agent_activate' or 'agent_get_active'. However, it doesn't explicitly differentiate from all siblings beyond the shorthand aspect.

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 like 'agent_activate' or 'agent_list'. It mentions 'quick switch' and 'shorthand', implying it's for fast agent changes, but offers no explicit context, prerequisites, or exclusions for usage compared to other tools.

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