Skip to main content
Glama
Bigred97

aemo-mcp

latest

Retrieve the most recent interval from NEM datasets, covering 5-minute dispatch prices, 30-minute rooftop PV, or daily summaries. Filter results by region or fuel type.

Instructions

Return the most recent interval(s) for a NEM dataset.

For 5-min feeds (dispatch_price, dispatch_region, interconnector_flows, generation_scada): returns the most recent 5-minute interval, typically 1-2 minutes after the interval close.

For 30-min feeds (rooftop_pv, predispatch_30min): the most recent half-hour.

For daily feeds (daily_summary): yesterday's data.

Examples: # Current NSW spot price resp = await latest("dispatch_price", filters={"region": "NSW1"})

# Current generation mix in QLD
resp = await latest("generation_scada", filters={"region": "QLD1"})

# Current flow across Heywood
resp = await latest("interconnector_flows", filters={"interconnector": "V-SA"})

Returns: DataResponse with one observation per filtered (dimension, metric) tuple at the most recent interval. stale=True flag indicates the most recent interval is older than 2× the feed cadence (NEMWEB delay).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYesDataset ID like 'dispatch_price'. Use the search endpoint or search tool to discover.
filtersNoOptional filter dict. Same shape as get_data — narrow to a region, interconnector, fuel, etc.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYes
dataset_nameYes
queryNo
interval_startNo
interval_endNo
periodNoCanonical {start, end} period bounds for cross-sister consumers. Populated alongside aemo-specific interval_start/interval_end.
unitNo
row_countNoNumber of observation rows in records.
recordsNo
csvNo
sourceNoAustralian Energy Market Operator
attributionNoSource: Australian Energy Market Operator (AEMO), NEMWEB. Used under AEMO's Copyright Permissions (general permission for any purpose with accurate attribution). https://aemo.com.au/privacy-and-legal-notices/copyright-permissions
source_urlYes
retrieved_atYes
staleNo
stale_reasonNo
truncated_atNo
server_versionNo
Behavior4/5

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

With no annotations, the description provides good behavioral details: interval cadence per feed type, delay characteristics, and the stale flag. Lacks explicit mention that it is a read-only operation, but the context is clear.

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

Conciseness5/5

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

The description is well-organized with sections for different feed types, a concise list of examples, and no unnecessary words. Every sentence contributes to understanding.

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 that an output schema exists, the description provides sufficient context about the return type (DataResponse with stale flag) and covers all relevant feed types. No gaps identified.

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

Parameters4/5

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

Schema has 100% coverage with descriptions and examples, but the description adds value by explaining the meaning in context, such as how filters narrow results and which dataset IDs apply.

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 precisely states the tool's purpose: 'Return the most recent interval(s) for a NEM dataset.' It differentiates from siblings like get_data (historical) and search_datasets by focusing on the latest single observation.

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 clearly tells when to use the tool (to get the most recent interval) and provides examples. However, it does not explicitly mention when not to use it or contrast with siblings like get_data for historical queries.

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/Bigred97/aemo-mcp'

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