Skip to main content
Glama
bchoi-qwe

aeso-mcp

by bchoi-qwe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Operating Reserve Offer Control

get_operating_reserve_offer_control
Read-onlyIdempotent

Fetch a historical AESO Operating Reserve Offer Control report for a specific date, with paginated results and prices in CAD/MWh, volumes in MW. Useful for accessing official Alberta reserve offer data.

Instructions

Returns one historical AESO Operating Reserve Offer Control report date as paginated blocks. Reports are released with a 60-day delay; prices are CAD/MWh, volumes are MW, and timestamps use America/Edmonton.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesRequest one AESO report date with bounded output pagination.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesPagination state for a stable in-memory report result.
blocksYes
metadataYesProvenance and semantic metadata attached to dataset responses.
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • 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"
+]
  2. Addedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds valuable beyond-annotation context: the 60-day delay, units (CAD/MWh and MW), timezone (America/Edmonton), and paginated delivery, which help the agent interpret results and set expectations.

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 two sentences with no filler. It front-loads the action and resource, then packs essential constraints (delay, units, timezone, pagination) into the remaining sentence. 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?

With an output schema present, rich annotations, and a single required parameter, the description covers the key operational constraints: historical scope, delay, units, timezone, and pagination. A minor gap is that it does not define what 'Operating Reserve Offer Control' means, but the title and sibling context provide enough orientation for an agent.

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%, and the request object description already explains bounded output pagination. The main tool description adds units and timezone but does not add parameter-specific semantics beyond what the schema already documents; the baseline of 3 is appropriate.

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 clearly states a specific verb ('Returns'), a specific resource ('one historical AESO Operating Reserve Offer Control report date'), and a distinguishing behavior ('as paginated blocks'). It is easily distinguishable from sibling operating reserve tools, which cover prices, forecasts, or activations rather than offer control report dates.

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

Usage Guidelines3/5

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

The description implies usage for historical report dates and notes the 60-day release delay, giving useful context about when data will be available. However, it does not explicitly state when to prefer this tool over alternatives such as get_operating_reserve_prices or get_operating_reserve_forecast, nor does it mention any exclusions.

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

Deploy Server

Other Tools