Skip to main content
Glama

list_icon_providers_tool

Read-only

Discover available icon providers and their categories. Get an overview of the icon catalog structure with provider details and category counts.

Instructions

    Lists all available icon providers and their categories.

    This tool provides an overview of the icon catalog structure,
    showing available providers and their service categories.

    Returns:
        dict: Provider information with categories and icon counts
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for list_icon_providers_tool, registered via @mcp.tool decorator. It uses the fetcher's get_icon_providers() method to retrieve and return information about all available icon providers and their categories.
    async def list_icon_providers_tool(ctx: Optional[Context] = None) -> Dict[str, Any]:
        """
        Lists all available icon providers and their categories.
    
        This tool provides an overview of the icon catalog structure,
        showing available providers and their service categories.
    
        Returns:
            dict: Provider information with categories and icon counts
        """
        try:
            if ctx:
                await ctx.info("Fetching icon provider information")
    
            # Get fetcher instance
            fetcher = get_fetcher()
    
            # Get provider information
            provider_info = await fetcher.get_icon_providers()
    
            if provider_info is None:
                error_msg = "Failed to fetch icon provider information. The service may be temporarily unavailable."
                if ctx:
                    await ctx.error(error_msg)
                return {"error": error_msg}
    
            if ctx:
                await ctx.info(
                    f"Retrieved information for {len(provider_info.get('providers', {}))} icon providers"
                )
            return provider_info
    
        except Exception as e:
            error_msg = f"Error fetching icon provider information: {str(e)}"
            if ctx:
                await ctx.error(error_msg)
            return {"error": error_msg}
  • The tool is registered with FastMCP via the @mcp.tool() decorator inside register_fetch_icons_tool(), which is called from server.py line 73.
    @mcp.tool(
        annotations={
            "title": "List Available Icon Providers",
            "readOnlyHint": True,
            "description": "Lists all available icon providers and categories from the icon catalog",
        }
    )
  • The IlographContentFetcher.get_icon_providers() helper method that fetches and parses the icon catalog, organizing icons by provider with category counts and total counts.
    async def get_icon_providers(self) -> Optional[Dict[str, Any]]:
        """
        Get information about all available icon providers and their categories.
    
        Returns:
            Dictionary with provider information or None if catalog unavailable
        """
        try:
            # Fetch catalog content
            catalog_content = await self.fetch_icon_catalog()
            if catalog_content is None:
                return None
    
            # Parse catalog into structured data
            all_icons = self._parse_icon_catalog(catalog_content)
    
            # Organize by provider
            providers: Dict[str, Any] = {}
            for icon in all_icons:
                provider = icon["provider"]
                category = icon["category"]
    
                if provider not in providers:
                    providers[provider] = {"categories": {}, "total_icons": 0}
    
                if category not in providers[provider]["categories"]:
                    providers[provider]["categories"][category] = 0
    
                providers[provider]["categories"][category] += 1
                providers[provider]["total_icons"] += 1
    
            return {
                "providers": providers,
                "total_providers": len(providers),
                "message": f"Found {len(providers)} icon providers with {len(all_icons)} total icons",
            }
    
        except Exception as e:
            logger.error(f"Error getting icon providers: {e}")
            return None
  • The tool annotations define the schema/metadata for list_icon_providers_tool, including title, readOnlyHint, and description.
        annotations={
            "title": "List Available Icon Providers",
            "readOnlyHint": True,
            "description": "Lists all available icon providers and categories from the icon catalog",
        }
    )
    async def list_icon_providers_tool(ctx: Optional[Context] = None) -> Dict[str, Any]:
        """
        Lists all available icon providers and their categories.
    
        This tool provides an overview of the icon catalog structure,
        showing available providers and their service categories.
    
        Returns:
            dict: Provider information with categories and icon counts
        """
        try:
            if ctx:
                await ctx.info("Fetching icon provider information")
    
            # Get fetcher instance
            fetcher = get_fetcher()
    
            # Get provider information
            provider_info = await fetcher.get_icon_providers()
    
            if provider_info is None:
                error_msg = "Failed to fetch icon provider information. The service may be temporarily unavailable."
                if ctx:
                    await ctx.error(error_msg)
                return {"error": error_msg}
    
            if ctx:
                await ctx.info(
                    f"Retrieved information for {len(provider_info.get('providers', {}))} icon providers"
                )
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description adds context by specifying the return format (dict with categories and icon counts). This is useful but minimal; the tool's behavior is straightforward.

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?

Three efficient sentences, front-loaded with the main purpose. No wasted words.

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

Completeness5/5

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

Given no parameters, no output schema, and a simple task, the description fully conveys what the tool returns and its purpose.

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?

No parameters exist, so schema coverage is 100%. The description doesn't need to add parameter info. Baseline for 0 parameters is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists all available icon providers and their categories, using specific verbs ('lists', 'provides an overview') and resource ('icon providers', 'icon catalog structure'). It implicitly distinguishes from sibling tools like search_icons_tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use or not use, but the tool is simple and read-only. The description implies usage for getting an overview, but does not mention alternatives or prerequisites.

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

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