Skip to main content
Glama

nempulse

by au.com.nempulse
OverviewDiscussionsAdmin

List NEM price events

list_events
Read-onlyIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax events to return (default 10, max 500).
offsetNoSkip this many events, for paging (default 0).
regionNoNEM region code: NSW1, QLD1, SA1 (South Australia), TAS1 or VIC1.
date_toNoOptional. Only events starting on or before this date, YYYY-MM-DD.
date_fromNoOptional. Only events starting on or after this date, YYYY-MM-DD.
event_typeNoOptional event type filter.
include_responsesNoAlso return per-battery responses for each event (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / date_from
      Added value: +{
+  "description": "Optional. Only events starting on or after this date, YYYY-MM-DD.",
+  "format": "date",
+  "type": "string"
+}
    • addedInput schema / properties / date_to
      Added value: +{
+  "description": "Optional. Only events starting on or before this date, YYYY-MM-DD.",
+  "format": "date",
+  "type": "string"
+}
    • addedInput schema / properties / event_type
      Added value: +{
+  "description": "Optional event type filter.",
+  "enum": [
+    "negative",
+    "elevated",
+    "spike",
+    "extreme"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / include_responses
      Added value: +{
+  "description": "Also return per-battery responses for each event (default false).",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max events to return (default 50, max 500)"New value: +"Max events to return (default 10, max 500)."
    • addedInput schema / properties / limit / maximum
      Added value: +500
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Skip this many events, for paging (default 0).",
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / region / description
      Previous value: -"NEM region, e.g. SA1 (optional)"New value: +"NEM region code: NSW1, QLD1, SA1 (South Australia), TAS1 or VIC1."
    • addedInput schema / properties / region / enum
      Added value: +[
+  "NSW1",
+  "QLD1",
+  "SA1",
+  "TAS1",
+  "VIC1"
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description adds orthogonal value: default ordering (newest first), the ~100 KB truncation behavior when include_responses is true, and the meaning of is_open. That is exactly the payload-risk context an agent needs before choosing include_responses.

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?

Front-loads the definition, then filtering, then the include_responses caveat and the sibling hand-off in a logical order. It is dense and somewhat long due to the event-type taxonomy, but each clause carries information an agent would otherwise have to guess.

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?

With no output schema, the description enumerates the returned fields (event_id, region, event_type, started_at, ended_at, duration_min, peak_rrp, avg_rrp, is_open) and warns about payload size, so nothing an agent needs to call and interpret this tool is missing.

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 coverage is 100%, so the baseline is 3. The description goes beyond it by defining the numeric price bands behind each event_type enum value and stating that filters combine (region, event_type, date range), which the schema alone does not convey.

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?

States a specific verb+resource (list NEM spot-price events) and immediately defines what an 'event' is, including the threshold logic and the four type buckets. This distinguishes it from siblings like query_nem_data and get_regional_prices without requiring schema inspection.

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

Usage Guidelines5/5

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

Explicitly routes the agent: set include_responses only when battery behavior is needed, keep limit small in that case, and use get_event_detail for a single event's responses. It names the alternative tool and the condition that selects it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All nempulse toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources