nempulse
Server Details
Australian NEM battery (BESS) data for AI agents: revenue, dispatch, FCAS, events. Free, no auth.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 14 tools
Most tools target a distinct resource+action, but there is real overlap between get_battery_detail, get_battery_revenue, get_battery_optimal and get_battery_mlf, and between get_network_access and get_battery_network_access. The descriptions resolve this explicitly (repeated 'use X for Y, not Z' guidance, e.g. 'this is the tool for total revenue questions'), which is effective but signals that the boundaries are not self-evident from the names alone.
All tools use snake_case with a consistent verb_noun shape: get_* for retrievals, list_* for reference/enumeration, query_* for the ad-hoc escape hatch. The battery-scoped tools consistently carry the battery_ prefix, making the single-unit vs fleet-wide split predictable from the name.
14 tools for a market-analytics domain covering fleet reference, per-unit detail, revenue, MLF, network access, events, prices, rankings and a simulator is well within a comfortable range. Each tool appears to earn its place, with no obvious redundant filler.
The surface covers the lifecycle well: reference lookup, per-unit metrics, revenue, optimal-dispatch benchmarking, loss factors, network access, event drill-down, regional prices and a simulator, plus query_nem_data as a catch-all. Gaps remain for intraday/5-minute price series and per-interval dispatch during events (both explicitly declared unavailable), which agents can only partially work around via the SQL tool.
Available Tools
14 toolsget_battery_detailBattery detailARead-onlyIdempotentInspect
Deep-dive metrics for one battery by DUID (e.g. HPR1 = Hornsdale): revenue, dispatch, SOC, FCAS. WARNING: rev_today, energy_rev_today, fcas_rev_today and contingency_fcas_rev_today are MONTH-TO-DATE by default, not daily (matching the rev_mtd keys in fcas_breakdown) — do not report them as 'today's revenue'. throughput_cycles, throughput_mwh, avg_dispatch_price, avg_charge_price and efficiency_pct cover the same window. Pass date_from and date_to (both required together) to scope this window explicitly, e.g. to a single day, instead of relying on the month-to-date default. For a true daily time series use get_battery_revenue. rte_pct is NOT window-scoped: it is the unit's latest measured round-trip efficiency (fitted from AEMO's reported energy storage against its dispatch over a trailing 30 days, refreshed weekly), and is null for units whose fit has not cleared its acceptance checks — null means 'not measured', never 'inefficient'. Also returns commercial_context (e.g. TOLLED, CONTRACTED) and commercial_note — ALWAYS check commercial_context before comparing this unit's revenue against another unit's: tolled/contracted units do not trade merchant and their spot figures are not comparable.
Inputs: duid (required), date_to, date_from.
get_battery_mlfBattery loss factors (MLF) by financial yearARead-onlyIdempotentInspect
Transmission loss factors (MLF) for one battery by financial year from FY2024-25: mlf_discharge (credits each MWh discharged), mlf_charge (bills each MWh charged), mlf_spread, and gross energy revenue at MLF 1.0 versus at the unit's loss factors (energy_rev_gross, energy_rev_mlf, mlf_effect, split into discharge_effect and charge_effect). The comparison holds dispatch fixed, so it is illustrative: a different loss factor would have changed how the unit bid. A charge factor below 1 lowers charging cost, so mlf_effect can be positive. source says whether the factor came from AEMO's published MLF list or DUDETAILSUMMARY.
Inputs: duid (required).
get_battery_network_accessBattery network access (binding constraints)ARead-onlyIdempotentInspect
Network access for one battery by DUID over a date window: the same exposure shares as get_network_access, a 12-block (2-hour, market time) time-of-day profile for discharge and charge limits, the five constraints that bound most often with AEMO's descriptions (these name the lines and outages involved), commissioning_days, and the current financial year's loss factors with their effect on energy revenue versus an MLF of 1.0. Exposure, not lost revenue. A high all-interval share with a low top-price share means the limits fall in low-price hours (often midday). Minimum window 30 days (shorter is widened); data from July 2024.
Inputs: duid (required), date_to (required), date_from (required).
get_battery_optimalActual vs optimal dispatch revenueARead-onlyIdempotentInspect
Actual vs LP-optimal dispatch revenue, per-DUID summary, over a date range (energy-only, perfect-foresight benchmark). NOT a revenue-total source — use get_battery_revenue for that. Both the 'actual' AND the 'optimal' figures here are MLF-adjusted (get_battery_revenue's is gross) — the LP's objective is solved on MLF-adjusted prices, not just settled at them afterward — and both cover solved LP days only (days where the solver failed are dropped from both), so the two tools' totals will not match even for the same DUID and date range. The requested date_to may also be silently truncated to the latest date with sufficient fleet-wide LP coverage. Pass duid to restrict to one battery — omitting it scans every DUID and can time out even on a ~3-week range; even a single-DUID, single-month scan has been observed to time out, so keep date ranges short and retry narrower on a timeout.
Inputs: date_to (required), date_from (required), duid.
get_battery_revenueBattery daily revenueARead-onlyIdempotentInspect
Daily gross-spot revenue by market (energy + FCAS) for one battery (DUID) over a date range. Daily grain only. This is the tool for total revenue questions — use get_battery_optimal only for the actual-vs-perfect-foresight benchmark, not as a revenue source (its 'actual' figure is MLF-adjusted and solved-days-only, so it will not match this tool's totals). Each day also carries energy_rev_mlf_adjusted (null if the LP backcast hasn't run for that day yet, not zero) alongside the gross energy_rev, so MLF-adjusted figures are available here too without switching tools.
Inputs: duid (required), date_to (required), date_from (required).
get_event_detailPrice event detailARead-onlyIdempotentInspect
One price event by event_id (take the id from list_events), with the response of every battery that was online, ranked by est_revenue. Event fields are as in list_events. Each battery row has duid, station, region, response (DISCH = discharging, CHRG = charging, IDLE, OFFLINE = no availability), avg_mw (positive is discharge), peak_mw, est_revenue (energy only, sum of MW times price over the event, gross, not MLF-adjusted; excludes FCAS), soc_pct at start and soc_pct_end, availability_mw, fcas_mw (average FCAS commitment), plus is_commissioning, unit_class and peer_comparable. Check those labels before comparing units. Per-interval dispatch during the event is not exposed.
Inputs: id (required).
get_fleet_summaryNEM battery fleet summaryARead-onlyIdempotentInspect
Fleet-wide snapshot for the NEM battery fleet: unit_count, active_unit_count, total_mw, total_mwh, fleet_rev_mtd, avg_efficiency_pct, last_interval and spot_prices (latest price per region, $/MWh). Covers month-to-date unless date_from and date_to are given. fleet_rev_mtd is gross spot revenue (energy + FCAS + FPP) over that window, whatever its length, despite the name. avg_efficiency_pct is dollar-weighted actual energy revenue as a share of the perfect-foresight optimum (a capture rate), null if the optimisation has not run for the window. Commissioning units are excluded from the efficiency figure unless include_commissioning is true. For one battery use get_battery_detail; for a ranking use get_rankings.
Inputs: date_to, date_from, include_commissioning.
get_network_accessFleet network access (binding constraints)ARead-onlyIdempotentInspect
How often binding network (transmission) constraints limited each NEM battery's access to the energy market over a date window, split by direction. Per unit: pct_discharge_limited, pct_charge_limited, pct_top_price_discharge_limited (share of the top-10% regional price intervals that were discharge-limited), pct_neg_price_charge_limited (share of negative-price intervals that were charge-limited), commissioning_days and top_constraint (AEMO constraint ID, direction, description). Also the constraints behind the most fleet exposure. This is EXPOSURE, not lost revenue: a binding constraint caps what a unit could do, not what it wanted to do, and AEMO often resolves it by moving other units — never present these as lost dollars or lost dispatch. Commissioning units (commissioning_days > 0) dispatch on test schedules; leave them out of comparisons. Check commercial_context: TOLLED/CONTRACTED units dispatch for an offtaker. Minimum window is 30 days (shorter is widened); data from July 2024; constraint data lags about two days (days_covered vs days_requested). Large response (every unit); for one battery use get_battery_network_access.
Inputs: date_to (required), date_from (required).
get_rankingsBattery capture-rate rankingsARead-onlyIdempotentInspect
League table of merchant NEM batteries over a date range, ranked by capture rate by default (actual revenue as a share of the forecast-informed benchmark; capture_perfect_pct is the share of the perfect-foresight ceiling). Each row has rank, duid, station, region, capacity, duration_band, capture_fc_pct, capture_perfect_pct, rev_per_mw_day, rev_per_mwh_day, total_rev, cycles_per_day and movement against the previous period of equal length. total_rev is MLF-adjusted over LP-solved days (through lp_through), so it differs from get_battery_revenue's gross every-day total. Units still commissioning and CONTRACTED or TOLLED units are listed under excluded, not ranked, unless include_arrangement is true (their spot revenue is not their commercial return). Check unit_class and peer_comparable before reading a gap as performance. It scans the whole fleet twice, so keep the range to a month or less; it can be slow or time out on long ranges. For one unit's revenue use get_battery_revenue.
Inputs: date_to (required), date_from (required), limit, region, +3 more.
get_regional_pricesRegional daily price summaryARead-onlyIdempotentInspect
Daily minimum, maximum and mean regional reference price (RRP, $/MWh) for one NEM region over a date range. Daily summary only: the raw 5-minute price series is not exposed (it is published by AEMO on NEMWEB). Use it for price context around revenue or events. For individual price spikes use list_events.
Inputs: region (required), date_to (required), date_from (required).
get_simulator_revenueHypothetical battery revenueARead-onlyIdempotentInspect
Modelled revenue for a hypothetical 1 MW battery of a given duration in one region (not a real unit), from NEMPulse's optimal-dispatch model on real prices. Returns P10/P50/P90 revenue for three tiers: realistic (forecast-informed result scaled by the capture ratio real batteries achieve, the only tier to use as a project case), forecast_informed (idealised execution on AEMO's public price forecast) and perfect (an unreachable ceiling). Also energy_share and fcas_share, a monthly series, and the real-unit cohorts behind the FCAS cap and the capture ratio. Gross spot revenue only, before costs, degradation and financing. It is a screening estimate, not a forecast of future revenue.
Inputs: region (required), duration (required).
list_bess_unitsList NEM battery unitsARead-onlyIdempotentInspect
Reference list of every NEM-registered grid-scale battery. Call this first to turn a station name into the DUID the other tools need. Returns the whole fleet in one response (no filters): DUID, station, region, MW/MWh, MLF, coordinates, is_commissioning, commercial_context, unit_class, peer_comparable, rev_per_mw_yr. Caveats on the fields follow. rev_per_mw_yr is trailing 365-day energy + FCAS revenue (NOT FPP), gross (no MLF), divided by Max Cap MW, then annualised over the days the unit actually had dispatch data — not over a fixed 365-day denominator. This is a rough simulator guide, NOT a performance ranking. It is distorted for any unit with is_commissioning=true or commissioned within the last 365 days, because that span-annualisation extrapolates a few months of ramp-up behaviour out to a full year (scale-up factors of 1.5x-2.4x are live in the current data), which magnifies both weak and negative figures rather than diluting them — do NOT try to 'correct' it by rescaling to the unit's operating span, as that double-counts the annualisation. It is also inflated for small FCAS-primary units, and structurally biased against longer-duration units (shorter-duration units can concentrate power into the highest-price intervals). Do not use it to compare units, rank performance, or answer 'which battery earns most' — use get_battery_revenue over a matched window, or get_battery_optimal for capture. Before comparing any two units' revenue, check BOTH labels on each. commercial_context (TOLLED/CONTRACTED) means the unit does not trade merchant, so its spot revenue is not comparable; a null here means no publicly documented arrangement was found, NOT that the unit is confirmed merchant — only an explicit MERCHANT value means that, and most units are null. unit_class is the structural label (STANDALONE/HYBRID/NETWORK-SUPPORT/MICRO): peer_comparable is false for the latter three, whose dispatch answers to a co-located generator, a non-market obligation, or sub-10MW FCAS granularity rather than to price. Never pool a peer_comparable=false unit into a cross-unit statistic or ranking. Null until the first background refresh completes.
Inputs: no named parameters.
list_eventsList NEM price eventsARead-onlyIdempotentInspect
List NEM spot-price events, newest first. An event is a run of 5-minute intervals in one region where the price stays above $500/MWh or below -$200/MWh (short gaps are bridged), typed by its peak price: negative (below -$200), elevated (peak $500 to $1,000), spike ($1,000 to $5,000) or extreme ($5,000 and above). Each event has event_id, region, event_type, started_at, ended_at, duration_min, peak_rrp, avg_rrp and is_open (still ongoing). Filter by region, event_type and a date range. By default only event summaries are returned; set include_responses to true to also get how each battery behaved during each event, in which case keep limit small (response rows make the payload large and it is truncated at about 100 KB). Use get_event_detail for one event's battery responses.
Inputs: limit, offset, region, date_to, +3 more.
query_nem_dataAsk a question of the NEM dataARead-onlyIdempotentInspect
Last resort for ad hoc questions the other tools cannot answer. Not for live or current prices: NEMPulse publishes daily price summaries only; use get_regional_prices for daily min/max/mean RRP and AEMO NEMWEB DISPATCHPRICE for the live 5-minute feed. Takes a plain-English question, generates SQL over NEMPulse's tables, and returns the SQL, the result rows and a short explanation. It is the slowest tool (can take close to a minute) and it is AI-generated, so check the returned SQL before relying on a number. Scope each question to about one region-month or less: wider aggregates (a full year by region, or per-day top-N across all regions) risk exceeding the 8 second SQL limit, and a longer wait does not help. For per-day top-N or bottom-N questions, ask for a window function (ROW_NUMBER or RANK) rather than a per-day subquery, which has been seen to silently return all-null rows. Queryable data: dispatch prices, daily revenue, optimal dispatch, battery price profiles and market events. The market analysis tables (monthly spreads, regressions, correlations) are not reachable here.
Inputs: question (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
AEMO MCP server for Australia's National Electricity Market: prices, generation, FCAS, bids.
Live US power market prices, load, generation, weather and permits for AI agents.
Real-time electricity price signals for AI agents. Spot prices, cheapest hours, and contract recommendations. 31 countries across Europe and Oceania. No authentication required.
Real-time electricity prices for AI agents. 40+ countries, 100+ zones. No auth required.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query and explain Australian National Electricity Market data from nemweb.com.au, covering price spikes, negative-price runs, interconnector flows and limits, binding constraints, and generation by fuel or unit, with live updates and every response stating its time convention, units, caveats, data freshness, and source AEMO file.AGPL 3.0
- AlicenseAqualityFmaintenanceOne-call Australian energy-market plumbing via AEMO — cited, structured responses for market data and analysis, not a data broker.5196 PyPIMIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible AI applications to retrieve structured Belgian electricity generation, load, imbalance, and price data from Elia Open Data, with deterministic energy calculations and data-quality checks.8MIT
- AlicenseNot gradedqualityBmaintenance87+ specialized tools for German and European energy data. Direct AI access to Marktstammdatenregister (MaStR), ENTSO-E, Redispatch 2.0, and Grid Operations for utilities and datacenters.2GPL 3.0
Glama MCP Gateway
Add one secure layer between your agents and this server.