Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Build renderer card config

card_builder_renderer_card_config
Read-onlyIdempotent

Builds the Lovelace card config dict for a Card Builder card, with optional slot entities and actions. Use this config to embed an existing card on a dashboard.

Instructions

Build the Lovelace card config dict that renders a Card Builder card.

Pure computation — assembles {"type": "custom:card-builder-renderer-card", "card_id": ...} plus the optional slot_entities/slot_actions keys; makes no call to Home Assistant.

Use when: embedding an existing Card Builder card on a dashboard. Not for: adding the resulting config to a dashboard — pass it as card_config to dashboards_add_card_to_section (sections views) or dashboards_add_card_to_view (masonry/panel views). Returns: {"type": "custom:card-builder-renderer-card", "card_id": ..., "slot_entities": {...}, "slot_actions": {...}} — the latter two keys are omitted when not provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idYesId of the Card Builder card to render, from card_builder_list_cards.
slot_actionsNoPer-instance overrides for the card's action slots. Omit to use the card's own defaults.
slot_entitiesNoMaps each slot id defined in the card to a HA entity_id, e.g. {'climate': 'climate.salon'}. Omit for no slot bindings.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.25.1
    • addedInput schema / properties / card_id / description
      Added value: +"Id of the Card Builder card to render, from card_builder_list_cards."
    • addedInput schema / properties / slot_actions / description
      Added value: +"Per-instance overrides for the card's action slots. Omit to use the card's own defaults."
    • addedInput schema / properties / slot_entities / description
      Added value: +"Maps each slot id defined in the card to a HA entity_id, e.g. {'climate': 'climate.salon'}. Omit for no slot bindings."
  2. Addedv0.18.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world. The description adds meaningful context beyond that: 'Pure computation — makes no call to Home Assistant,' which tells the agent this cannot fail on HA connectivity or cause side effects, plus an explicit return shape. Not a full 5 since it doesn't discuss validation errors or edge cases, but the added context is genuinely useful.

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?

Front-loads the core purpose, then uses labeled 'Use when', 'Not for', and 'Returns' segments. Every sentence carries routing or output information; nothing is padding.

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 an output schema exists, the description need not detail return values further, and the annotations cover safety. Combined with precise routing to the two dashboard-insertion siblings, an agent has everything needed to invoke this correctly in a pipeline.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents card_id, slot_entities, and slot_actions in detail. The description restates the optional keys and their omission behavior ('omitted when not provided'), which echoes the schema defaults rather than adding new syntax or format guidance. Baseline 3 is appropriate.

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 ('Build the Lovelace card config dict that renders a Card Builder card') and pins down the exact output shape. It clearly distinguishes itself from dashboard-mutation siblings by naming them explicitly.

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

Usage Guidelines5/5

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

Provides explicit 'Use when' and 'Not for' guidance, including the exact follow-up tools (dashboards_add_card_to_section for sections views, dashboards_add_card_to_view for masonry/panel views). Nothing is left to inference about when to pick this tool.

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