Skip to main content
Glama

agent_get_active

Retrieve the currently active AI agent from persistent memory storage to maintain context across sessions.

Instructions

Get the currently active agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'agent_get_active' tool. Initializes the AgentManager if needed, retrieves the currently active agent using am.getActiveAgent(), and returns its details as JSON or a message if no agent is active.
    case 'agent_get_active': {
      await am.initialize();
      const activeAgent = am.getActiveAgent();
      
      if (!activeAgent) {
        return {
          content: [
            {
              type: 'text',
              text: 'No agent currently active. Use agent_activate to select one.'
            }
          ]
        };
      }
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              active: {
                id: activeAgent.id,
                name: activeAgent.name,
                category: activeAgent.metadata.category,
                role: activeAgent.metadata.role
              }
            }, null, 2)
          }
        ]
      };
    }
  • src/index.ts:378-385 (registration)
    Registration of the 'agent_get_active' tool in the tools array, including its name, description, and empty input schema. This makes it available via listTools.
    {
      name: 'agent_get_active',
      description: 'Get the currently active agent',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Input schema for agent_get_active tool: accepts an empty object (no parameters).
    inputSchema: {
      type: 'object',
      properties: {}
    }
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 tool retrieves information ('Get'), implying a read-only operation, but doesn't specify what data is returned (e.g., agent ID, name, status), whether it requires authentication, or if there are rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, clear sentence with no wasted words. It is front-loaded with the core purpose ('Get the currently active agent'), making it immediately understandable. Every word earns its place, and there is no unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'active agent' means in this context, what information is returned, or how this tool fits into the broader agent management system. For a tool that likely returns structured data about an agent, more context is needed to be fully useful.

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

Parameters4/5

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

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to explain parameters, so it meets the baseline expectation. No additional parameter information is required or provided.

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 ('Get') and the target resource ('the currently active agent'), making the purpose immediately understandable. It distinguishes from siblings like agent_list (which presumably lists all agents) and agent_switch_quick (which changes the active agent). However, it doesn't specify what information about the active agent is retrieved, leaving some ambiguity.

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 an agent must be active), compare it to agent_list for broader listings, or explain its role in workflows with tools like agent_activate or agent_switch_quick. Usage is implied but not explicitly stated.

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