Skip to main content
Glama

equip-toolset

Apply a predefined toolset configuration to filter and access tools efficiently within the Hypertool-MCP server.

Instructions

Equip a saved toolset configuration to filter available tools

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the toolset to equip

Implementation Reference

  • Core implementation of equipToolset method in ToolsetManager that loads the specified toolset from persistent storage, validates it, sets it as the active toolset, updates preferences, generates info, and returns structured response. This is the actual logic executed when the tool is called.
    async equipToolset(toolsetName: string): Promise<EquipToolsetResponse> {
      try {
        // Import the function here to avoid circular imports
        const preferences = await import("../../../config/preferenceStore.js");
        const loadToolsetsFromPreferences = preferences.loadStoredToolsets;
        const saveLastEquippedToolset = preferences.saveLastEquippedToolset;
    
        const stored = await loadToolsetsFromPreferences();
        const toolsetConfig = stored[toolsetName];
    
        if (!toolsetConfig) {
          return { success: false, error: `Toolset "${toolsetName}" not found` };
        }
    
        const validation = this.setCurrentToolset(toolsetConfig);
        if (!validation.valid) {
          return {
            success: false,
            error: `Invalid toolset: ${validation.errors.join(", ")}`,
          };
        }
    
        // Save this as the last equipped toolset
        await saveLastEquippedToolset(toolsetName);
    
        // Generate toolset info with current status
        const toolsetInfo = await this.generateToolsetInfo(toolsetConfig);
    
        // Event is already emitted by setConfig()
        return {
          success: true,
          toolset: toolsetInfo,
        };
      } catch (error) {
        return {
          success: false,
          error: `Failed to load toolset: ${error instanceof Error ? error.message : String(error)}`,
        };
      }
    }
  • MCP Tool definition for 'equip-toolset' including name, description, and input schema requiring a 'name' parameter.
    export const equipToolsetDefinition: Tool = {
      name: "equip-toolset",
      description: "Equip a saved toolset configuration to filter available tools",
      inputSchema: {
        type: "object" as const,
        properties: {
          name: {
            type: "string",
            description: "Name of the toolset to equip",
          },
        },
        required: ["name"],
        additionalProperties: false,
      },
    };
  • Registry where createEquipToolsetModule factory is imported and added to CONFIG_TOOL_FACTORIES array for configuration tools.
    import { createListSavedToolsetsModule } from "./tools/list-saved-toolsets.js";
    import { createEquipToolsetModule } from "./tools/equip-toolset.js";
    import { createDeleteToolsetModule } from "./tools/delete-toolset.js";
    import { createUnequipToolsetModule } from "./tools/unequip-toolset.js";
    import { createGetActiveToolsetModule } from "./tools/get-active-toolset.js";
    import { createAddToolAnnotationModule } from "./tools/add-tool-annotation.js";
    import { createExitConfigurationModeModule } from "../common/exit-configuration-mode.js";
    import { createListPersonasModule } from "./persona/list-personas.js";
    
    /**
     * Registry of all configuration tool factories
     */
    export const CONFIG_TOOL_FACTORIES: ToolModuleFactory[] = [
      createListAvailableToolsModule,
      createBuildToolsetModule,
      createListSavedToolsetsModule,
      createEquipToolsetModule,
      createDeleteToolsetModule,
      createUnequipToolsetModule,
      createGetActiveToolsetModule,
      createAddToolAnnotationModule,
      createListPersonasModule, // Persona management tool
      createExitConfigurationModeModule,
    ];
  • Routing logic in ConfigToolsManager.handleToolCall that intercepts 'equip-toolset' calls and delegates to the active IToolsetDelegate (ToolsetManager or PersonaManager).equipToolset, wrapping the result in MCP response format.
    case "equip-toolset": {
      const result = await delegate.equipToolset(args?.name);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result),
          },
        ],
        structuredContent: result,
      };
    }
  • Instantiation of all configuration tool modules from factories in ConfigToolsManager constructor's registerTools method, including equip-toolset module.
    for (const factory of CONFIG_TOOL_FACTORIES) {
      const module = factory(this.dependencies, this.onModeChangeRequest);
      this.toolModules.set(module.toolName, module);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'filter available tools' which hints at read-only behavior, but doesn't clarify if this is a mutation (e.g., changing system state), what permissions are needed, or what happens on success/failure. For a tool with zero annotation coverage, this is insufficient behavioral disclosure.

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 directly states the tool's purpose without redundancy. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place.

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 complexity (toolset management), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'equip' entails operationally, how filtering works, or what the agent should expect after invocation. This leaves significant gaps for effective tool use.

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?

Schema description coverage is 100%, with the single parameter 'name' documented as 'Name of the toolset to equip'. The description adds no additional parameter semantics beyond this, such as format examples or constraints. With high schema coverage, the 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 ('equip') and the resource ('saved toolset configuration'), specifying that it 'filters available tools'. This provides a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get-active-toolset' or 'build-toolset', which prevents a perfect score.

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., needing a saved toolset first), exclusions, or comparisons to siblings like 'unequip-toolset' or 'get-active-toolset'. This leaves the agent without context for tool selection.

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

Related 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/toolprint/hypertool-mcp'

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