Feature: Hybrid MCP tool mode
Currently Kyber exposes only 4 fixed tools. This means the external LLM always delegates to \kyber_ask\ and cannot directly call HA intents.
Proposal
Add a config option \mcp_tool_mode:
- \�sk_only\ (current default) — only kyber_ask + helpers
- \dynamic\ — expose one tool per HA intent/domain (like HA native MCP)
- \hybrid\ — expose both kyber_ask AND dynamic tools
In hybrid mode, capable LLMs (GPT-4o, Claude) can choose: use \kyber_ask\ for complex natural-language requests, or call a specific intent tool directly for simple deterministic actions.
Benefits of hybrid
- Fast path: \HassTurnOn\ for simple on/off (no AI loop overhead)
- Smart path: \kyber_ask\ for ambiguous/complex requests
- External LLM can plan multi-step actions using native HA tools
- Parallel tool calls become possible
Closes gaps: multi-step chaining, parallel execution, token efficiency for simple actions.
Feature: Hybrid MCP tool mode
Currently Kyber exposes only 4 fixed tools. This means the external LLM always delegates to \kyber_ask\ and cannot directly call HA intents.
Proposal
Add a config option \mcp_tool_mode:
In hybrid mode, capable LLMs (GPT-4o, Claude) can choose: use \kyber_ask\ for complex natural-language requests, or call a specific intent tool directly for simple deterministic actions.
Benefits of hybrid
Closes gaps: multi-step chaining, parallel execution, token efficiency for simple actions.