Skip to main content
Glama

list_entities

Retrieve Home Assistant entities filtered by domain, search term, or specific fields.

Instructions

Get a list of Home Assistant entities with optional filtering

Args: domain: Optional domain to filter by (e.g., 'light', 'switch', 'sensor') search_query: Optional search term to filter entities by name, id, or attributes (Note: Does not support wildcards. To get all entities, leave this empty) limit: Maximum number of entities to return (default: 100) fields: Optional list of specific fields to include in each entity detailed: If True, returns all entity fields without filtering

Returns: A list of entity dictionaries with lean formatting by default

Examples: domain="light" - get all lights search_query="kitchen", limit=20 - search entities domain="sensor", detailed=True - full sensor details

Best Practices: - Use lean format (default) for most operations - Prefer domain filtering over no filtering - For domain overviews, use domain_summary_tool instead of list_entities - Only request detailed=True when necessary for full attribute inspection - To get all entity types/domains, use list_entities without a domain filter, then extract domains from entity_ids

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNo
search_queryNo
limitNo
fieldsNo
detailedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'list_entities' tool. Decorated with @mcp.tool() and @async_handler(). Accepts optional domain, search_query, limit, fields, and detailed parameters. Logs the request, handles wildcard '*' search query, and delegates to get_entities() in app/hass.py.
    @mcp.tool()
    @async_handler("list_entities")
    async def list_entities(
        domain: Optional[str] = None, 
        search_query: Optional[str] = None, 
        limit: int = 100,
        fields: Optional[List[str]] = None,
        detailed: bool = False
    ) -> List[Dict[str, Any]]:
        """
        Get a list of Home Assistant entities with optional filtering
        
        Args:
            domain: Optional domain to filter by (e.g., 'light', 'switch', 'sensor')
            search_query: Optional search term to filter entities by name, id, or attributes
                         (Note: Does not support wildcards. To get all entities, leave this empty)
            limit: Maximum number of entities to return (default: 100)
            fields: Optional list of specific fields to include in each entity
            detailed: If True, returns all entity fields without filtering
        
        Returns:
            A list of entity dictionaries with lean formatting by default
        
        Examples:
            domain="light" - get all lights
            search_query="kitchen", limit=20 - search entities
            domain="sensor", detailed=True - full sensor details
        
        Best Practices:
            - Use lean format (default) for most operations
            - Prefer domain filtering over no filtering
            - For domain overviews, use domain_summary_tool instead of list_entities
            - Only request detailed=True when necessary for full attribute inspection
            - To get all entity types/domains, use list_entities without a domain filter, 
              then extract domains from entity_ids
        """
        log_message = "Getting entities"
        if domain:
            log_message += f" for domain: {domain}"
        if search_query:
            log_message += f" matching: '{search_query}'"
        if limit != 100:
            log_message += f" (limit: {limit})"
        if detailed:
            log_message += " (detailed format)"
        elif fields:
            log_message += f" (custom fields: {fields})"
        else:
            log_message += " (lean format)"
        
        logger.info(log_message)
        
        # Handle special case where search_query is a wildcard/asterisk - just ignore it
        if search_query == "*":
            search_query = None
            logger.info("Converting '*' search query to None (retrieving all entities)")
        
        # Use the updated get_entities function with field filtering
        return await get_entities(
            domain=domain, 
            search_query=search_query, 
            limit=limit,
            fields=fields,
            lean=not detailed  # Use lean format unless detailed is requested
        )
  • app/server.py:246-247 (registration)
    The tool is registered via the @mcp.tool() decorator on line 246 in app/server.py, which registers 'list_entities' as an MCP tool with the FastMCP server.
    @mcp.tool()
    @async_handler("list_entities")
  • The get_entities() helper function in app/hass.py that performs the actual API call. It fetches all states from HA's /api/states endpoint, enriches with area data, filters by domain and search query, applies limits, and formats output with lean/field filtering.
    async def get_entities(
        domain: Optional[str] = None, 
        search_query: Optional[str] = None, 
        limit: int = 100,
        fields: Optional[List[str]] = None,
        lean: bool = True
    ) -> List[Dict[str, Any]]:
        """
        Get a list of all entities from Home Assistant with optional filtering and search
        
        Args:
            domain: Optional domain to filter entities by (e.g., 'light', 'switch')
            search_query: Optional case-insensitive search term to filter by entity_id, friendly_name or other attributes
            limit: Maximum number of entities to return (default: 100)
            fields: Optional list of specific fields to include in each entity
            lean: If True (default), returns token-efficient versions with minimal fields
        
        Returns:
            List of entity dictionaries, optionally filtered by domain and search terms,
            and optionally limited to specific fields
        """
        # Get all entities directly
        client = await get_client()
        response = await client.get(f"{HA_URL}/api/states", headers=get_ha_headers())
        response.raise_for_status()
        entities = response.json()
    
        # Enrich each entity with area data. One bulk template call covers
        # the whole list regardless of size.
        areas = await get_all_areas(client)
        for entity in entities:
            entity["area"] = areas.get(entity["entity_id"])
    
        # Filter by domain if specified
        if domain:
            entities = [entity for entity in entities if entity["entity_id"].startswith(f"{domain}.")]
        
        # Search if query is provided
        if search_query and search_query.strip():
            search_term = search_query.lower().strip()
            filtered_entities = []
            
            for entity in entities:
                # Search in entity_id
                if search_term in entity["entity_id"].lower():
                    filtered_entities.append(entity)
                    continue
                    
                # Search in friendly_name
                friendly_name = entity.get("attributes", {}).get("friendly_name", "").lower()
                if friendly_name and search_term in friendly_name:
                    filtered_entities.append(entity)
                    continue
                    
                # Search in other common attributes (state, area_id, etc.)
                if search_term in entity.get("state", "").lower():
                    filtered_entities.append(entity)
                    continue
                    
                # Search in other attributes
                for attr_name, attr_value in entity.get("attributes", {}).items():
                    # Check if attribute value can be converted to string
                    if isinstance(attr_value, (str, int, float, bool)):
                        if search_term in str(attr_value).lower():
                            filtered_entities.append(entity)
                            break
            
            entities = filtered_entities
        
        # Apply the limit
        if limit > 0 and len(entities) > limit:
            entities = entities[:limit]
        
        # Apply field filtering if requested
        if fields:
            # Use explicit field list when provided
            return [filter_fields(entity, fields) for entity in entities]
        elif lean:
            # Apply domain-specific lean fields to each entity
            result = []
            for entity in entities:
                # Get the entity's domain
                entity_domain = entity["entity_id"].split('.')[0]
                
                # Start with basic lean fields
                lean_fields = DEFAULT_LEAN_FIELDS.copy()
                
                # Add domain-specific important attributes
                if entity_domain in DOMAIN_IMPORTANT_ATTRIBUTES:
                    for attr in DOMAIN_IMPORTANT_ATTRIBUTES[entity_domain]:
                        lean_fields.append(f"attr.{attr}")
                
                # Filter and add to result
                result.append(filter_fields(entity, lean_fields))
            
            return result
        else:
            # Return full entities
            return entities
  • Input schema/type annotations for the list_entities tool: domain (Optional[str]), search_query (Optional[str]), limit (int, default 100), fields (Optional[List[str]]), detailed (bool, default False). Return type is List[Dict[str, Any]].
    async def list_entities(
        domain: Optional[str] = None, 
        search_query: Optional[str] = None, 
        limit: int = 100,
        fields: Optional[List[str]] = None,
        detailed: bool = False
    ) -> List[Dict[str, Any]]:
Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses that search_query doesn't support wildcards, defaults (limit=100), and that returning 'lean formatting' by default vs detailed. But it doesn't mention pagination behavior, potential errors, or output structure beyond 'entity dictionaries'. The disclosure is adequate but not thorough.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured into Args, Returns, Examples, and Best Practices sections. It is front-loaded with the core purpose. While somewhat lengthy, every section provides valuable information without being excessively verbose. It could be slightly streamlined but is well-organized.

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 presence of an output schema (not provided), the description adequately covers return format and usage scenarios. It includes best practices and comparisons to an alternative tool. It addresses all 5 parameters and provides examples. However, it doesn't mention pagination or maximum limits for the limit parameter, leaving minor gaps.

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?

Schema description coverage is 0%, but the description's 'Args' section explains each parameter with details (e.g., 'Does not support wildcards' for search_query, default values, types). It adds significant meaning beyond the schema's type/default-only information, though it could be more concise for some parameters.

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 'Get a list of Home Assistant entities with optional filtering', specifying both the verb and resource. It mentions an alternative (domain_summary_tool) for domain overviews, providing some sibling differentiation. However, it does not explicitly distinguish from other similar siblings like search_entities_tool or get_entities_by_area, so it loses a point for full differentiation.

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

Usage Guidelines4/5

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

The description includes a 'Best Practices' section that advises when to use this tool vs domain_summary_tool, and provides guidance on preferring domain filtering and using lean format. It also tells how to get all entities by leaving the search query empty. However, it doesn't cover all sibling tools (e.g., search_entities_tool) so it's not fully comprehensive.

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/voska/hass-mcp'

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