# OUTPUT FORMATTING FOR USER
**CRITICAL: Always format MCP tool output for readability!**
When MCP tools return data, DON'T show raw JSON to user. Format it nicely.
---
## Examples
### 1. Entity Analysis
β **BAD:** Show 7000 lines of JSON
β
**GOOD:**
```
π Your Home Assistant has:
- 238 total entities
- 76 sensors (temperature, battery, system status)
- 7 climate devices (TRVs)
- 35 switches
- 12 automations + 5 scripts
Main rooms: Office (21), Bathroom (19), Kitchen (17)
```
### 2. Add-on Lists
β **BAD:** 83 add-ons JSON dump
β
**GOOD:**
```
π¦ Available Add-ons (83 total):
Popular:
- Zigbee2MQTT (a0d7b954_zigbee2mqtt)
- Node-RED (a0d7b954_nodered)
- ESPHome (hassio_esphome)
```
### 3. Logs
β **BAD:** Raw JSON array
β
**GOOD:**
```
π Recent logs:
[21:03:35] β
Dashboard registered
[21:03:46] β οΈ Restart failed: 504 (normal during restart)
```
### 4. Dashboard Operations
β **BAD:** `{"success": true, "data": {...}}`
β
**GOOD:**
```
β
Dashboard "Heating Now" created!
- File: heating-now.yaml
- Registered in configuration.yaml
- HA restarting...
- Refresh UI to see dashboard in sidebar!
```
---
## General Rules
- Use emojis for visual clarity (π₯ β
β οΈ π)
- Show key information, hide implementation details
- Format lists, tables, and hierarchies clearly
- Highlight important values (counts, statuses, errors)
- Add context and next steps for user
---
## When to Show Raw Data
- User explicitly asks for "raw data" or "JSON"
- Debugging/troubleshooting scenarios
- Developer mode requests