tesla-powerwall
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POWERWALL_HOST | Yes | Your Powerwall gateway IP or hostname | |
| POWERWALL_EMAIL | No | Optional email | |
| POWERWALL_PASSWORD | Yes | Last 5 digits of gateway serial number or custom password | |
| POWERWALL_USERNAME | Yes | Usually 'customer' |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| powerwall_loginA | Authenticate with the Powerwall gateway and obtain an access token |
| powerwall_logoutA | Logout and expire the current authentication token |
| powerwall_get_meters_aggregatesB | Get current readings from meters measuring solar, grid, battery, and home power |
| powerwall_get_system_statusB | Get overall system status and information |
| powerwall_get_soeB | Get state of energy (battery charge percentage) |
| powerwall_get_site_infoB | Get site information including nominal system energy and power |
| powerwall_get_statusB | Get Powerwall status including version and uptime |
| powerwall_get_device_typeB | Get device type information |
| powerwall_get_customerB | Get customer registration information |
| powerwall_get_powerwallsB | Get list of Powerwalls and their status |
| powerwall_get_operationA | Get current operation mode settings |
| powerwall_set_operationB | Set operation mode (self_consumption, backup, autonomous, etc.) |
| powerwall_get_grid_statusB | Get grid connection status |
| powerwall_get_installerB | Get installer information |
| powerwall_get_solarsB | Get solar array information |
| powerwall_get_networksB | Get WiFi network information |
| powerwall_get_metersB | Get detailed meter information for all meters |
| powerwall_get_configC | Get system configuration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools map to distinct resources, but several read-only getters overlap in purpose, such as get_status vs get_system_status and get_meters vs get_meters_aggregates. An agent may struggle to choose between status-related endpoints without deeper API knowledge.
All tools use a consistent powerwall_ prefix with snake_case verb_noun names. The only non-get tools are login, logout, and set_operation, which clearly follow the same predictable action-based pattern.
18 tools is on the heavier side but appropriate for a Powerwall gateway server that exposes many distinct API resources. Each tool appears to represent a real endpoint, so the count is justified rather than bloated.
The server covers authentication, status, meters, battery state, grid status, operation settings, configuration, and installer details. The main gap is limited write operations beyond setting operation mode, but for monitoring and basic control the surface is largely complete.