Skip to main content
Glama

delete-toolset

Remove a specific toolset configuration from the hypertool-mcp server by providing its name and confirming the deletion to ensure precision and safety.

Instructions

Delete a saved toolset configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoConfirm deletion (required to actually delete)
nameYesName of the toolset to delete

Implementation Reference

  • The execute function (handler) for the 'delete-toolset' MCP tool. It invokes the toolsetManager's deleteToolset method with the provided name and confirmation flag, then formats the result as MCP content.
    handler: async (args: any) => {
      const deleteResult = await deps.toolsetManager.deleteToolset(args?.name, {
        confirm: args?.confirm,
      });
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(deleteResult),
          },
        ],
        structuredContent: deleteResult,
      };
    },
  • The Tool definition object for 'delete-toolset', including name, description, and inputSchema for validation (requires 'name', optional 'confirm').
    export const deleteToolsetDefinition: Tool = {
      name: "delete-toolset",
      description: "Delete a saved toolset configuration",
      inputSchema: {
        type: "object" as const,
        properties: {
          name: {
            type: "string",
            description: "Name of the toolset to delete",
          },
          confirm: {
            type: "boolean",
            description: "Confirm deletion (required to actually delete)",
          },
        },
        required: ["name"],
        additionalProperties: false,
      },
    };
  • Central registry of configuration tool factories, including 'createDeleteToolsetModule' which is imported from './tools/delete-toolset.js' (line 13). This array is used by ConfigToolsManager to instantiate and register the tools.
    export const CONFIG_TOOL_FACTORIES: ToolModuleFactory[] = [
      createListAvailableToolsModule,
      createBuildToolsetModule,
      createListSavedToolsetsModule,
      createEquipToolsetModule,
      createDeleteToolsetModule,
      createUnequipToolsetModule,
      createGetActiveToolsetModule,
      createAddToolAnnotationModule,
      createListPersonasModule, // Persona management tool
      createExitConfigurationModeModule,
    ];
  • In ConfigToolsManager, the registerTools method instantiates all factories from CONFIG_TOOL_FACTORIES (including delete-toolset) and registers them into the toolModules Map, which provides getMcpTools() and handleToolCall() for the MCP server.
    private registerTools(): void {
      logger.debug("Registering configuration tools");
    
      // Create and register each configuration tool module from the registry
      for (const factory of CONFIG_TOOL_FACTORIES) {
        const module = factory(this.dependencies, this.onModeChangeRequest);
        this.toolModules.set(module.toolName, module);
      }
    
      logger.info(`Registered ${this.toolModules.size} configuration tools`);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions deletion but fails to detail critical aspects like permissions required, whether deletion is reversible, confirmation requirements beyond the 'confirm' parameter, or error handling. This leaves significant gaps for a destructive operation.

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, direct sentence that states the tool's purpose without unnecessary words. It is front-loaded and efficient, making it easy to understand at a glance, with no wasted verbiage.

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 destructive nature and lack of annotations or output schema, the description is insufficient. It does not cover behavioral traits like safety warnings, return values, or error conditions, leaving the agent with incomplete information for proper invocation in a complex environment.

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, clearly documenting both parameters ('name' and 'confirm'). The description does not add any semantic details beyond what the schema provides, such as explaining the 'confirm' parameter's role in safety or naming conventions. Baseline 3 is appropriate as the schema handles the parameter documentation adequately.

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 ('Delete') and the resource ('a saved toolset configuration'), making the purpose immediately understandable. It distinguishes from siblings like 'list-saved-toolsets' or 'build-toolset' by specifying deletion. However, it doesn't explicitly differentiate from potentially similar destructive operations among siblings, keeping it at 4 rather than 5.

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, such as 'unequip-toolset' or other siblings. It lacks context about prerequisites, dependencies, or scenarios where deletion is appropriate, offering only a basic statement of function without usage context.

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