aeso-mcp

Overview Schema Source Related Servers Discussions Admin

Get Generation

get_generation

Read-onlyIdempotent

Get Alberta electricity generation data: current fuel-mix snapshot (MW by fuel) or historical wind/solar hourly generation, including renewable share.

Instructions

Returns Alberta generation data. Omit start/end for the current fuel-mix snapshot (all fuels, MW). Provide start and end for historical wind and solar hourly generation. Renewable share uses wind + solar + hydro over total generation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes	Request generation / fuel-mix data. Without a date range, returns the current CSD fuel mix (all fuels). With a date range, returns historical wind and solar generation where available.

Output Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	Pagination state for a stable in-memory report result.
`metadata`	Yes	Provenance and semantic metadata attached to dataset responses.
`snapshot`	No
`warnings`	No
`intervals`	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"
+]

Changed17 schema fields changedv0.2.0Aug 24, 2026

addedInput schema / properties / request / properties / limit

Added value: +{
+  "default": 500,
+  "maximum": 2000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / request / properties / offset

Added value: +{
+  "default": 0,
+  "minimum": 0,
+  "type": "integer"
+}

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
+}

addedOutput schema / properties / page

Added value: +{
+  "additionalProperties": false,
+  "description": "Pagination state for a stable in-memory report result.",
+  "properties": {
+    "limit": {
+      "type": "integer"
+    },
+    "next_offset": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "returned": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "offset",
+    "limit",
+    "returned",
+    "total"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "metadata"
-]New value: +[
+  "page",
+  "metadata"
+]

First observedv0.1.1Aug 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful behavioral context: the snapshot includes all fuels in MW, historical data is hourly wind/solar, and renewable share is computed as wind + solar + hydro over total generation. Pagination and limit behavior are not mentioned but are available in the schema.

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?

Three sentences with no wasted words: purpose first, then conditional usage, then a metric definition. Front-loaded and every sentence contributes to the caller's understanding.

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?

For a tool with a nested request schema and an output schema, the description covers the key behavioral modes and the renewable-share definition. It does not explain pagination or the exact output structure, but the schema and annotations fill those gaps, so nothing critical 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% and the nested request schema already explains the two date-range modes. The description enhances this by explicitly telling the user to omit or provide start/end and by defining the renewable-share calculation. Limit and offset are left to schema defaults, which is acceptable.

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 and resource ('Returns Alberta generation data') and clearly distinguishes the two operating modes: current fuel-mix snapshot vs historical wind/solar hourly generation. This makes it separable from sibling tools like get_generation_capacity or analyze_generation_mix without needing to inspect them.

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?

Gives explicit, actionable usage guidance: omit start/end for the current fuel-mix snapshot, and provide them for historical wind and solar generation. It does not explicitly contrast with sibling tools such as get_historical_generation, but the parameter-based conditions are unambiguous.

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

Deploy Server