Skip to main content
Glama

list-saved-toolsets

Retrieve detailed configurations of saved toolsets, including server settings and tool counts, to manage and optimize tool usage on the hypertool-mcp server.

Instructions

List all saved toolset configurations with detailed information including server configurations and tool counts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if the operation failed
successYesWhether the operation was successful
toolsetsYesArray of toolset information

Implementation Reference

  • Tool module factory and handler implementation that delegates to toolsetManager.listSavedToolsets() and returns MCP-formatted response
    export const createListSavedToolsetsModule: ToolModuleFactory = (
      deps
    ): ToolModule => {
      return {
        toolName: "list-saved-toolsets",
        definition: listSavedToolsetsDefinition,
        handler: async (
          // eslint-disable-next-line @typescript-eslint/no-unused-vars
          args: any
        ) => {
          const listResult = await deps.toolsetManager.listSavedToolsets();
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(listResult),
              },
            ],
            structuredContent: listResult,
          };
        },
      };
    };
  • Tool definition with name, description, input schema (no params), and output schema
    export const listSavedToolsetsDefinition: Tool = {
      name: "list-saved-toolsets",
      description:
        "List all saved toolset configurations with detailed information including server configurations and tool counts",
      inputSchema: {
        type: "object" as const,
        properties: {},
        additionalProperties: false,
      },
      outputSchema: {
        type: "object" as const,
        properties: {
          success: {
            type: "boolean",
            description: "Whether the operation was successful",
          },
          toolsets: {
            type: "array",
            description: "Array of toolset information",
            items: toolsetInfoSchema as any,
          },
          error: {
            type: "string",
            description: "Error message if the operation failed",
          },
        },
        required: ["success", "toolsets"],
      },
    };
  • Registry array CONFIG_TOOL_FACTORIES that includes the list-saved-toolsets tool factory
    export const CONFIG_TOOL_FACTORIES: ToolModuleFactory[] = [
      createListAvailableToolsModule,
      createBuildToolsetModule,
      createListSavedToolsetsModule,
      createEquipToolsetModule,
      createDeleteToolsetModule,
      createUnequipToolsetModule,
      createGetActiveToolsetModule,
      createAddToolAnnotationModule,
      createListPersonasModule, // Persona management tool
      createExitConfigurationModeModule,
    ];
  • Direct handler implementation in ConfigToolsManager.handleToolCall for list-saved-toolsets, routing to active toolset delegate
    case "list-saved-toolsets": {
      const result = await delegate.listSavedToolsets();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result),
          },
        ],
        structuredContent: result,
      };
    }
  • Core implementation in ToolsetManager.listSavedToolsets() that loads toolsets from user preferences and generates detailed info using generateToolsetInfo()
    async listSavedToolsets(): Promise<ListSavedToolsetsResponse> {
      try {
        const preferences = await import("../../../config/preferenceStore.js");
        const loadToolsetsFromPreferences = preferences.loadStoredToolsets;
        const stored = await loadToolsetsFromPreferences();
    
        // Get saved toolsets from preferences
        const savedToolsets = await Promise.all(
          Object.values(stored).map((config) => this.generateToolsetInfo(config))
        );
    
        return {
          success: true,
          toolsets: savedToolsets,
        };
      } catch (error) {
        return {
          success: false,
          toolsets: [],
          error: `Failed to list toolsets: ${error instanceof Error ? error.message : String(error)}`,
        };
      }
    }
Behavior3/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. It discloses that the tool lists configurations with 'detailed information including server configurations and tool counts', which adds useful context about return content. However, it doesn't mention behavioral traits like pagination, rate limits, or authentication needs, leaving gaps for a read 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, efficient sentence that front-loads the core action ('List all saved toolset configurations') and adds specific details ('with detailed information including server configurations and tool counts'). Every word earns its place with no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (simple read operation with no parameters) and the presence of an output schema (which handles return values), the description is reasonably complete. It specifies the resource and details included in the output, though it could benefit from more behavioral context like usage scenarios or limitations.

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 lack of inputs. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. Baseline is 4 for zero parameters, as it avoids unnecessary details.

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 verb 'List' and resource 'all saved toolset configurations', specifying the scope. It distinguishes from siblings like 'get-active-toolset' by listing all saved ones, but doesn't explicitly differentiate from 'list-available-tools' which might list different resources.

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 guidance is provided on when to use this tool versus alternatives like 'get-active-toolset' for the currently active toolset or 'list-available-tools' for available tools. The description implies usage for retrieving saved configurations but lacks explicit context or exclusions.

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