Skip to main content
Glama

list_icons

Retrieve all available Hugeicons icons for integration into platforms. This tool provides a complete list to help developers find and use appropriate icons in their projects.

Instructions

Get a list of all available Hugeicons icons

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that executes the list_icons tool logic: ensures icons are cached/loaded from API and returns the JSON-formatted list.
    private async handleListIcons() {
      try {
        await this.ensureIconsLoaded();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(this.iconsCache, null, 2),
            },
          ],
        };
      } catch (error) {
        if (error && typeof error === 'object' && 'isAxiosError' in error) {
          throw new McpError(
            ErrorCode.InternalError,
            `Failed to list icons: ${(error as any).message}`
          );
        }
        throw error;
      }
    }
  • src/index.ts:71-79 (registration)
    Tool registration in ListToolsRequestSchema handler, defining name, description, and input schema.
    {
      name: "list_icons",
      description: "Get a list of all available Hugeicons icons",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • src/index.ts:158-159 (registration)
    Dispatch routing in CallToolRequestSchema handler to the list_icons handler function.
    case "list_icons":
      return await this.handleListIcons();
  • Input schema definition for the list_icons tool (empty object, no required parameters).
    inputSchema: {
      type: "object",
      properties: {},
      required: [],
    },
  • Supporting helper function to load and cache the full list of icons from the external API, called by the handler.
    private async ensureIconsLoaded() {
      if (this.iconsCache) return;
    
      try {
        const response = await axios.get<{ icons: IconInfo[] }>("https://hugeicons.com/api/icons");
        this.iconsCache = response.data.icons;
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          "Failed to load icons data"
        );
      }
    }
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 states the action but doesn't add context about what 'all available' entails (e.g., pagination, rate limits, authentication needs, or response format). This leaves significant gaps for a tool that likely returns a large dataset.

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 any fluff. It's front-loaded and appropriately sized for a simple tool, earning its place with zero waste.

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 (a list operation with no output schema) and lack of annotations, the description is incomplete. It doesn't address behavioral aspects like response format, data volume, or potential limitations, which are crucial for an agent to use this 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, aligning with the schema. A baseline of 4 is applied since it doesn't add unnecessary information.

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 'Get' and the resource 'list of all available Hugeicons icons', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_icons' or 'get_icon_glyphs', 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 like 'search_icons' or 'get_icon_glyphs'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent with minimal direction.

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/hugeicons/mcp-server'

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