Skip to main content
Glama
homeassistant-ai

Home Assistant MCP Server

Official
by homeassistant-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Available Services

ha_list_services
Read-onlyIdempotent

Discover Home Assistant services and callable actions; filter by domain or search query, paginate results, and retrieve full parameter details.

Instructions

List available Home Assistant services with optional pagination and detail control.

Discovers services/actions that can be called via ha_call_service.

EXAMPLES:

  • Light services with full parameter details: ha_list_services(domain="light", detail_level="full")

  • Search: ha_list_services(query="temperature")

  • Next page: ha_list_services(offset=50)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax services to return per page
queryNoSearch in service names and descriptions.
domainNoFilter by domain (e.g., 'light', 'switch', 'climate').
fieldsNoReturn only the specified top-level response keys to reduce response size (e.g. ["services"]). None = full response. Available keys: success, domains, services, total_count, count, offset, limit, has_more, next_offset, detail_level, filters_applied.
offsetNoNumber of services to skip for pagination
detail_levelNo'summary': name, description, domain, service, and target when the service has one. 'full': additionally include parameter field schemas.summary
service_fieldsNoProject each service record to only the specified keys. E.g. ["name", "description"] returns slim service records. None = full records. Unknown keys yield empty records. Available keys: name, description, domain, service, target (when present), fields (full mode only).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv8.6.0
    • changedInput schema / properties / detail_level / description
      Previous value: -"'summary': service name + description only (default). 'full': include parameter field schemas."New value: +"'summary': name, description, domain, service, and target when the service has one. 'full': additionally include parameter field schemas."
    • changedInput schema / properties / fields / description
      Previous value: -"Return only the specified top-level response keys to reduce response size (e.g. [\"services\"]). None = full response (default). Available keys: success, domains, services, total_count, count, offset, limit, has_more, next_offset, detail_level, filters_applied."New value: +"Return only the specified top-level response keys to reduce response size (e.g. [\"services\"]). None = full response. Available keys: success, domains, services, total_count, count, offset, limit, has_more, next_offset, detail_level, filters_applied."
    • changedInput schema / properties / limit / description
      Previous value: -"Max services to return per page (default: 50)"New value: +"Max services to return per page"
    • changedInput schema / properties / offset / description
      Previous value: -"Number of services to skip for pagination (default: 0)"New value: +"Number of services to skip for pagination"
    • changedInput schema / properties / service_fields / description
      Previous value: -"Project each service record to only the specified keys. E.g. [\"name\", \"description\"] returns slim service records. None = full records (default). Unknown keys yield empty records. Available keys: name, description, domain, service, fields (full mode only), target (full mode only)."New value: +"Project each service record to only the specified keys. E.g. [\"name\", \"description\"] returns slim service records. None = full records. Unknown keys yield empty records. Available keys: name, description, domain, service, target (when present), fields (full mode only)."
  2. First observedv7.14.2

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds the discovery-vs-invocation relationship and the pagination/detail-control behavior, but these largely restate what the schema already documents, so it adds only modest extra context.

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?

Two short sentences plus three front-loaded one-line examples; every line earns its place. Slightly verbose in the examples format but nothing is wasted.

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?

With an output schema present, 100% schema coverage, and rich annotations, the description only needs to establish purpose and routing. It does that, though it could say more about pagination limits interacting with the total result set.

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 coverage is 100%, so the baseline is 3. The examples go beyond the schema descriptions by demonstrating concrete argument shapes for domain, query, offset, and detail_level (e.g. detail_level="full"), which helps an agent pick values correctly.

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?

States a specific verb and resource ('List available Home Assistant services') and explicitly frames the tool's role in the workflow: discovering services/actions that can then be called via ha_call_service. This distinguishes it cleanly from the sibling ha_call_service, which performs the call.

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 EXAMPLES block gives concrete when-to-use patterns (filter by domain, search, paginate) and the second sentence routes the agent to ha_call_service for the actual invocation. There is no explicit statement of when NOT to use it or an alternative discovery path, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools