VaDa Genius

Use this when the user asks what VaDa Genius recommends next: solar, battery, EV, tariff, automation, or contracted-power opportunities. It returns read-only opportunity cards with evidence, assumptions, missing data, risks, and next actions for an explicit date range.

solarbrain_get_genius_opportunities

Use this for Smart/EV installations when the user asks 'que hay encendido ahora', what VaDa has switched on now, which flexible loads are active, how much controlled power is running, or asks for a list/table of active devices. Use user_summary_es and active_assets for user-facing wording, locations, power, and timing fields when available; avoid technical IDs and avoid saying 'activos controlados encendidos'.

solarbrain_get_active_control_state

Use this when the user asks to test Auth0, verify SSO, check which SolarBrain user is logged in, or confirm whether ChatGPT is sending an authenticated OAuth token to the MCP server. This tool requires OAuth when Auth0 is enabled.

solarbrain_get_authenticated_user

Use this when the user asks whether the battery will charge fully, expected state of charge, evening discharge risk, battery forecast for today, or battery evolution by hour. Prefer human, by-hour reasoning when the backend returns hourly battery data.

solarbrain_get_battery_forecast

Use this when the user asks for an electricity bill, invoice estimate, monthly estimation process, current month cost, last month bill, import cost, export compensation, solar savings, wallet, or bill without solar comparison. Prefer bill_story.amount_to_pay_eur as the main payable amount, and use bill_story.formula_es plus bill_story.optimization_es to explain wallet, excedentes, and the goal of zero grid import with minimal export.

solarbrain_get_billing_estimate

Use this when the user only wants to know the current SolarBrain billing company, billing settings, tariff access, or contracted power settings. For Spanish 2.0TD, use contracted_power_context and keep P1 punta/llano separate from P2 valle; if only a single kW is visible, say that backend/MCP still lacks the split. This returns data only and does not open the editor UI.

solarbrain_get_billing_settings

Use this when the user asks what VaDa devices are configured, how they are named, where they are, their trigger availability, priority rules, average power, start/stop delays, or whether they are available now. This is read-only configuration; do not use it to switch devices on or off. Use display_name and location in answers, never technical IDs.

solarbrain_get_configured_assets

Use this when the user asks what is happening right now with PV production, home load, grid import/export, battery state, or current energy balance, including questions such as 'como esta la bateria ahora'. This returns data only, without the house widget.

solarbrain_get_current_energy

Use this when the user asks how today is going: solar generated so far, solar now, remaining forecast, battery outlook, export/import risk, or a short daily energy briefing. This is energy-only for the authenticated installation; use device tools for configured or active VaDa automations.

solarbrain_get_daily_outlook

Use this when the user asks about yesterday, today so far, a daily historical recap, or 'como fue ayer': solar generated, house consumption, grid import/export, battery behavior, device activation availability, and estimated variable cost. Do not answer that yesterday is unavailable before calling this tool for date_preset=yesterday.

solarbrain_get_daily_operational_summary

Use this when the user asks for the current electricity price, today's cheapest or most expensive hours, tomorrow's prices, or whether to move consumption today. For a complete hourly day, a graph or visual of today's prices, yesterday, a month, a custom range, or P1/P2/P3 averages, use solarbrain_get_energy_price_range. Price data comes from the published hourly catalog independently of household telemetry. Answer only the price question unless the user also asks about battery, weather, or automation.

solarbrain_get_energy_prices

Use this when the user asks for a complete hourly price series or graph for today, or for prices over explicit or inferable date ranges such as yesterday, today and yesterday, this month, last month, P1/P2/P3 averages, cheapest or most expensive hours in a range, or comparisons across days. date_from and date_to are inclusive local dates. This reads the published price catalog independently from household telemetry and returns at most one semantic visual_insight for short ranges. Answer only the price question unless the user asks for another energy decision.

solarbrain_get_energy_price_range

Use this for measured energy totals over a custom date range: year-to-date, a season, summer/winter windows, Semana Santa, or any from/to period. Provide inclusive YYYY-MM-DD dates and granularity. For cohort comparisons, use the cohort tool.

solarbrain_get_energy_range_summary

Use this for measured energy in a specific local time slot or hourly window: export, import, solar, house consumption, or battery behavior between two times on a target date. Infer today only when the user clearly asks about hoy.

solarbrain_get_energy_time_window

Use this when the user asks about this month, last month, monthly history, 'este mes', or 'el mes pasado'. This returns the backend semantic analytics summary: measured house consumption when DataDis import is valid as consumption, grid import/export, contract context, data-quality flags such as export_anomaly, and known missing dimensions. Prefer this over raw monthly telemetry for DataDis/grid_only installations.

solarbrain_get_period_operational_summary

Use this when the user asks about solar generation today, tomorrow, remaining solar energy, the best solar hour, or solar production windows.

solarbrain_get_solar_forecast

Use this when the user asks what to run today or tomorrow, in what order, or when to place flexible loads such as washing machine, dishwasher, dryer, oven, iron, pool, air conditioning, or a custom appliance. This is read-only advice and never switches devices. For SMART/EV installations, first separate loads already active/configured in VaDa from manual loads; do not tell the user to start something VaDa is already managing.

solarbrain_plan_flexible_loads

Use when the user asks when PV normally exceeds home consumption, reaches equilibrium, surplus starts or ends, whether the window is stable or fragmented, about today, at least X W, or one appliance. This is the only Energy Balance tool. Set threshold_w=0 unless an explicit margin is requested. Appliance profiles are typical hypotheses; never turn historical margin into guaranteed device power or full-cycle coverage. Insufficient is a valid result. Lead with the domestic conclusion and evidence; hide units and percentiles unless asked. Use at most one returned window-and-variability visual. Mention Smart only when explicitly permitted with compatibility and authorization.

solarbrain_get_energy_balance

Use this when the user asks whether to run a manual load now or today, such as a washing machine, dishwasher, dryer, oven, iron, or custom appliance.

solarbrain_recommend_manual_load

Use this only when the user asks for the visual house dashboard or explicitly asks about 'la casa' as a whole, for example 'muestrame la casa', 'como va la casa', or 'estado de la casa'. For direct questions about battery, solar production, grid, or what is switched on now, use the data/list tools instead.

solarbrain_show_live_house_snapshot