aeso-mcp

Overview Schema Source Related Servers Discussions Admin

Get Outages

get_outages

Read-onlyIdempotent

Retrieve hourly generator outage capacity by technology/fuel for a specified time range, including total megawatts and per-fuel breakdown.

Instructions

Returns hourly AESO generator outage capacity by technology/fuel for [start, end) (Total Outage MW plus per-fuel components). Timestamps: America/Edmonton. For transmission planned outages use get_approved_transmission_outages or get_long_range_transmission_outages.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes	Request hourly generator outage capacity by fuel/technology.

Output Schema

TableJSON Schema

Name	Required	Description
`outages`	Yes
`metadata`	Yes	Provenance and semantic metadata attached to dataset responses.
`warnings`	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"
+]

Changed36 schema fields changedv0.2.0Aug 24, 2026

changedInput schema / properties / request / description

Previous value: -"Request generator outage reports."New value: +"Request hourly generator outage capacity by fuel/technology."

changedOutput schema / description

Previous value: -"Generator outage observations."New value: +"Hourly generator outage capacity by technology/fuel."

addedOutput schema / properties / metadata / properties / available_series

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / metadata / properties / cache_age

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Age of the cached provider result in seconds when served."
+}

addedOutput schema / properties / metadata / properties / cache_hit
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```

addedOutput schema / properties / metadata / properties / completeness

Added value: +{
+  "default": "unknown",
+  "description": "Completeness of the requested observations or series.",
+  "enum": [
+    "complete",
+    "partial",
+    "degraded",
+    "empty",
+    "unknown"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / metadata / properties / expected_observation_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / metadata / properties / expected_observations

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / metadata / properties / finality

Added value: +{
+  "default": "unknown",
+  "description": "Whether published observations are final or still preliminary.",
+  "enum": [
+    "final",
+    "preliminary",
+    "unknown"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / metadata / properties / missing_observation_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / metadata / properties / missing_observations

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / metadata / properties / missing_series

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / metadata / properties / observation_type

Added value: +{
+  "default": "actual",
+  "description": "What kind of observation a response contains.\n\n``DataStatus`` predates this distinction and remains available for\ncompatibility.  ``observation_type`` should be used when a client needs\nto distinguish an actual observation from a forecast or a derived value.",
+  "enum": [
+    "actual",
+    "forecast",
+    "derived",
+    "unknown"
+  ],
+  "type": "string"
+}

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

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

addedOutput schema / properties / metadata / properties / served_at

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

changedOutput schema / properties / outages / items / description

Previous value: -"One generator outage observation."New value: +"Aggregated hourly generator outage capacity (GridStatus AESO shape)."

removedOutput schema / properties / outages / items / properties / asset_id

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

removedOutput schema / properties / outages / items / properties / asset_name

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

addedOutput schema / properties / outages / items / properties / biomass_and_other_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```
addedOutput schema / properties / outages / items / properties / coal_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```
addedOutput schema / properties / outages / items / properties / cogeneration_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```
addedOutput schema / properties / outages / items / properties / combined_cycle_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```
addedOutput schema / properties / outages / items / properties / energy_storage_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```

removedOutput schema / properties / outages / items / properties / fuel_type

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

addedOutput schema / properties / outages / items / properties / gas_fired_steam_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```
addedOutput schema / properties / outages / items / properties / hydro_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```

removedOutput schema / properties / outages / items / properties / maximum_capability_mw

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

addedOutput schema / properties / outages / items / properties / mothball_outage_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```

removedOutput schema / properties / outages / items / properties / outage_mw

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

addedOutput schema / properties / outages / items / properties / publication_time

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

removedOutput schema / properties / outages / items / properties / raw

Removed value: -{
-  "additionalProperties": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "number"
-      },
-      {
-        "type": "integer"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "type": "object"
-}

addedOutput schema / properties / outages / items / properties / simple_cycle_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```
addedOutput schema / properties / outages / items / properties / solar_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```
addedOutput schema / properties / outages / items / properties / total_outage_mw
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / outages / items / properties / wind_mw
```
Added value: +{
+  "default": 0,
+  "type": "number"
+}
```

changedOutput schema / properties / outages / items / required

Previous value: -[
-  "interval_start"
-]New value: +[
+  "interval_start",
+  "total_outage_mw"
+]

First observedv0.1.1Aug 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds valuable behavioral context beyond annotations: hourly granularity, half-open interval semantics, timezone (America/Edmonton), and that the response is a total with per-fuel breakdowns. No contradiction with annotations.

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 compact sentences deliver the essential purpose, interval behavior, timezone, and routing to alternatives. Every clause earns its place, and the most decision-relevant information is front-loaded.

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 the output schema exists, annotations cover safety traits, and the parameter schema documents the two inputs completely, the description adds the remaining needed semantics (hourly aggregation, interval boundaries, per-fuel components, timezone, and sibling differentiation). Nothing critical is missing for an agent to select and call this tool correctly.

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 coverage is 100%, and both parameters already have thorough descriptions including timezone handling and inclusive/exclusive semantics. The description reinforces hourly interval behavior but does not need to add parameter-level detail; the schema does the heavy lifting, so baseline 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 names a specific verb ('Returns'), a precise resource ('hourly AESO generator outage capacity by technology/fuel'), and the interval semantics ('[start, end)'). It also clarifies the output composition ('Total Outage MW plus per-fuel components'), which makes the tool's purpose unambiguous and distinct from the transmission outage tools.

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?

The description explicitly states when to use alternatives: 'For transmission planned outages use get_approved_transmission_outages or get_long_range_transmission_outages.' This directly differentiates generator outages from transmission outages, giving an agent clear routing guidance without needing to inspect sibling tools.

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

Deploy Server