Skip to main content
Glama

dashboards_get_dashboard_resources

Get Lovelace dashboard resources such as custom cards and CSS for managing your Home Assistant interface.

Instructions

Get Lovelace resources (custom cards, CSS).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler for dashboards_get_dashboard_resources tool. Decorated as @mcp.tool() on a FastMCP instance named 'dashboards'. Calls ha._ws_call('lovelace/resources') to fetch Lovelace resources (custom cards, CSS) via WebSocket.
    @mcp.tool()
    def get_dashboard_resources() -> list[dict]:
        """Get Lovelace resources (custom cards, CSS)."""
        return ha._ws_call("lovelace/resources")
  • FastMCP instance registration; the @mcp.tool() decorator registers get_dashboard_resources under the 'dashboards' MCP server.
    mcp = FastMCP("dashboards")
  • Helper function _ws_call that the handler delegates to; sends 'lovelace/resources' WebSocket message to Home Assistant.
    def _ws_call(msg_type: str, **kwargs) -> Any:
        try:
            asyncio.get_running_loop()
        except RuntimeError:
            return asyncio.run(_ws_call_async(msg_type, **kwargs))
        import concurrent.futures
        with concurrent.futures.ThreadPoolExecutor() as pool:
            return pool.submit(asyncio.run, _ws_call_async(msg_type, **kwargs)).result()
Behavior2/5

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

No annotations provided. Description does not disclose behavior beyond 'Get'. No mention of read-only nature, side effects, or response details. With an output schema, some context is implied but not stated.

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?

Single sentence with no filler. Front-loaded and efficient.

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?

For a parameterless get tool with output schema, the description is mostly complete. Could mention that it fetches current resources or that it is read-only, but overall sufficient.

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?

Input schema has no parameters; description clarifies the resource type (custom cards, CSS), adding meaning beyond the empty schema.

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?

Uses specific verb 'Get' and resource 'Lovelace resources' with examples (custom cards, CSS). Clearly distinguishes from sibling tools like dashboards_add_card_to_view or dashboards_get_dashboard_config.

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. Implies retrieval of resources, but lacks context like when to call instead of other dashboard tools.

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/Fistacho/ha-nexus-agent'

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