aeso-mcp

Overview Schema Source Related Servers Discussions Admin

Get Monthly Cumulative Net Revenue

get_monthly_cumulative_net_revenue

Read-onlyIdempotent

Retrieve the current AESO monthly cumulative net revenue report, showing cumulative CAD against annualized unavoidable costs and whether the secondary offer price limit trigger has been met.

Instructions

Returns the current AESO Monthly Cumulative Settlement Interval Net Revenue (MCSINR) public report. Includes cumulative CAD vs 1/6 annualized unavoidable costs and whether the secondary offer price limit trigger has been reached. Timestamps: America/Edmonton hour-ending intervals.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes	Request the current market-power mitigation public reports.

Output Schema

TableJSON Schema

Name	Required	Description
`metadata`	Yes	Provenance and semantic metadata attached to dataset responses.
`warnings`	No
`intervals`	Yes
`report_time`	No
`headroom_to_trigger_cad`	No
`latest_cumulative_net_revenue_cad`	No
`secondary_offer_price_limit_triggered`	No
`one_sixth_annualized_unavoidable_costs_cad`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Aug 28, 2026

changedOutput schema / properties / metadata / properties / provider / enum

Previous value: -[
-  "gridstatus",
-  "aeso_apim",
-  "aeso_public_report",
-  "derived"
-]New value: +[
+  "gridstatus",
+  "aeso_apim",
+  "aeso_public_report",
+  "aeso_csd_archive",
+  "derived"
+]

Addedv0.2.0Aug 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds useful behavioral context: the report is the current public report, includes cumulative CAD vs 1/6 annualized unavoidable costs, includes the trigger status, and uses America/Edmonton hour-ending interval timestamps.

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?

Two concise sentences with no filler. The first sentence identifies the tool's output; the second adds content and timezone details. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple one-parameter schema, the existing output schema, and the comprehensive annotations, the description is nearly complete. It clearly identifies what is returned and key formatting details. It lacks explicit usage-scenario guidance, but that is a relatively minor gap for this read-only report tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description does not add anything about the 'request' or 'current_only' parameters beyond what the schema already states.

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 names a specific verb ('Returns'), a specific resource ('AESO Monthly Cumulative Settlement Interval Net Revenue (MCSINR) public report'), and clarifies the report's key contents. This makes it easy to distinguish from the many sibling market-report tools.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. For example, it mentions the secondary offer price limit trigger, but does not direct agents to a dedicated sibling tool like get_secondary_offer_price_limit when that is the only needed value.

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

Deploy Server