Skip to main content
Glama
mouldiwarp

solax-cloud-mcp

by mouldiwarp

set_battery_self_use_mode

Set inverter battery to Self Use Mode with configurable minimum and maximum SOC and optional time-based charge/discharge periods to optimize energy use based on solar availability.

Instructions

Set inverter battery to Self Use Mode with configurable charging thresholds.

Self Use Mode is ideal for automated control based on conditions like weather. You can set minimum SOC (don't discharge below), maximum charge SOC (don't charge above), and optionally configure time-based charge/discharge periods (e.g., charge during peak solar, discharge during high-rate periods).

Example automation scenarios:

  • Reduce charging threshold on cloudy days to preserve grid import reserves

  • Increase charging threshold on clear days to maximize solar self-consumption

  • Prevent overnight charging from grid during expensive peak hours

Args: device_sn: Serial number of the inverter. If omitted, uses SOLAX_DEVICE_SN. min_soc: Minimum SOC (%), range [10, 100]. Battery won't discharge below this. Default: 10%. charge_upper_soc: Maximum charging SOC (%), range [10, 100]. Battery won't charge above this. Default: 100%. charge_from_grid_enable: Allow charging from grid (0=no, 1=yes). Default: 1 (enabled). charge_start_time_period1: Optional start time for charging period 1 (HH:MM format, e.g., "06:00"). charge_end_time_period1: Optional end time for charging period 1 (HH:MM format, e.g., "18:00"). discharge_start_time_period1: Optional start time for discharge period 1 (HH:MM format). discharge_end_time_period1: Optional end time for discharge period 1 (HH:MM format). enable_time_period2: Enable second time period (0=disabled, 1=enabled). Default: 0. charge_start_time_period2: Optional start time for charging period 2 (HH:MM format). charge_end_time_period2: Optional end time for charging period 2 (HH:MM format). discharge_start_time_period2: Optional start time for discharge period 2 (HH:MM format). discharge_end_time_period2: Optional end time for discharge period 2 (HH:MM format).

Returns: API response confirming the command was sent to the inverter.

Raises: ToolError: if the inverter is offline, credentials are invalid, or the API fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
min_socNo
device_snNo
charge_upper_socNo
enable_time_period2No
charge_end_time_period1No
charge_end_time_period2No
charge_from_grid_enableNo
charge_start_time_period1No
charge_start_time_period2No
discharge_end_time_period1No
discharge_end_time_period2No
discharge_start_time_period1No
discharge_start_time_period2No
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool sends a command to the inverter, returns an API response, and raises ToolError for offline inverter, invalid credentials, or API failure. It does not detail potential side effects on other settings, but overall transparency is good.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with a one-line summary, explanatory paragraph, example scenarios, and a clear list of arguments. It is slightly verbose but front-loads the purpose. No unnecessary sentences, but could be trimmed slightly.

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 13 parameters, no output schema, and no annotations, the description covers all aspects: parameter details, error conditions, usage scenarios. It is comprehensive enough for an agent to invoke the tool correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so description must compensate. It provides thorough details for all 13 parameters: defaults, ranges (e.g., min_soc [10,100]), formats (HH:MM for time periods), and explanations of each parameter's purpose. This fully compensates for the lack of schema descriptions.

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?

The description clearly states the tool sets inverter battery to Self Use Mode with configurable thresholds. It uses a specific verb ('Set') and resource ('inverter battery'), and distinguishes from sibling tool get_realtime_data which is read-only.

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

Usage Guidelines4/5

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

The description explains when Self Use Mode is ideal (automated control based on conditions) and provides example automation scenarios. It does not explicitly exclude other modes or provide alternatives, but given the sibling tool, context is clear. Score 4 for clear context without explicit exclusions.

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/mouldiwarp/solax-cloud-mcp'

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