Skip to main content
Glama

unequip-toolset

Unequip the current toolset to display all available tools for selection, enhancing accessibility and context within the hypertool-mcp server.

Instructions

Unequip the currently equipped toolset and show all available tools

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the unequip-toolset tool logic: unequips the current toolset via toolsetManager and returns a formatted success message announcing all tools are now available.
    handler: async (
      // eslint-disable-next-line @typescript-eslint/no-unused-vars
      args: any
    ) => {
      await deps.toolsetManager.unequipToolset();
      // ToolsetManager will emit 'toolsetChanged' event which triggers notifyToolsChanged()
    
      return {
        content: [
          {
            type: "text",
            text: "✅ **Toolset Unequipped**\n\nAll discovered tools are now available. The server's tool list has been reset to show all tools from connected servers.",
          },
        ],
      };
    },
  • The tool definition including name, description, and empty input schema (no parameters required).
    export const unequipToolsetDefinition: Tool = {
      name: "unequip-toolset",
      description:
        "Unequip the currently equipped toolset and show all available tools",
      inputSchema: {
        type: "object" as const,
        properties: {},
        additionalProperties: false,
      },
    };
  • Registration of the unequip-toolset module factory (createUnequipToolsetModule) in the central configuration tools registry array (CONFIG_TOOL_FACTORIES). This array is used to initialize and provide the config tools to the MCP server.
    export const CONFIG_TOOL_FACTORIES: ToolModuleFactory[] = [
      createListAvailableToolsModule,
      createBuildToolsetModule,
      createListSavedToolsetsModule,
      createEquipToolsetModule,
      createDeleteToolsetModule,
      createUnequipToolsetModule,
      createGetActiveToolsetModule,
      createAddToolAnnotationModule,
      createListPersonasModule, // Persona management tool
      createExitConfigurationModeModule,
    ];
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool unequips and shows available tools, but doesn't clarify if this is a read-only operation, if it requires specific permissions, what happens to the unequipped toolset (e.g., saved or lost), or any rate limits. This is inadequate for a mutation-like tool with zero annotation coverage.

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 primary action ('unequip') and includes the secondary effect. There is no wasted verbiage, and it directly communicates the tool's function without redundancy.

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 no annotations, no output schema, and the tool's complexity (involving state change and listing), the description is incomplete. It lacks details on behavioral traits (e.g., permissions, side effects), return values, or error conditions. This leaves significant gaps for an agent to use the tool effectively.

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 with 100% schema description coverage, so the schema fully documents the absence of inputs. The description adds no parameter-specific information, which is appropriate here. Baseline is 4 for zero parameters, as no compensation is needed.

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 ('unequip') and resource ('currently equipped toolset'), and mentions the secondary effect ('show all available tools'). It distinguishes from siblings like 'equip-toolset' and 'get-active-toolset' by focusing on removal rather than addition or retrieval. However, it doesn't explicitly contrast with all siblings (e.g., 'delete-toolset' also removes but permanently).

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage when switching from an equipped toolset to viewing available tools, but doesn't specify prerequisites (e.g., must have an active toolset) or compare to siblings like 'delete-toolset' for permanent removal. This leaves gaps in agent decision-making.

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